C
ChUIMonster
Guest
With all due respect I think you are perpetuating a myth. There is no check for ambiguity on a unique find -- I have never found an iota of evidence to support that contention. If the FIND is using a unique index there is no need to check anything -- the very nature of the index ensures that. If it is *not* a unique index then you should be using a statement that deals with multiple records such as FOR EACH. Even if I am wrong (I'll happily buy you lunch if you can show that I am) -- the statement is still misleading the next programmer to come along and, in my mind, the downside of misleading code far outweighs any hypothetical minuscule saving of execution time. FIND FIRST is waving a flag saying that there could be multiple records -- but then doing nothing about the possibility.
Continue reading...
Continue reading...