|
Make it easier. Put a trigger on the file. In that trigger intercept the
buffer and strip out all special characters and store it consistently. A
check constraint is ok, but instead of taking a baseball bat to the
person's knees why not automate it and say I know what you meant and store
it that way? Then, just run a one time conversion over the file to store
them all the same way. Less training involved. You don't have to modify
existing code to check the error on a write or update for a check
constraint violation. There's a lot of crappy code out there that assumes
that any error on a write must be because the row exists and then you
should perform an update.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.