×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




They say that everything can be found in the last place you look. It wasn't the scatter-gather; it was a failed update.

As it happens, I hadn't checked the job log for duplicate key collisions on the update. When I did, I found that every affected record had one, on a logical that was uniquely keyed on a generated key field that was regenerated in my program.

This particular key was designed, at least in part, to enforce uniqueness on the records. And some outside program writing and/or updating the file had been modifying that generated key in order to subvert the enforced uniqueness.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.