× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. January 2011

Re: CPF5035 used to be ignored, now causes SQL to fail

On 1/20/2011 9:13 AM, BMay@xxxxxxxxx wrote:
Exactly. Change the offending blanks to zeros within the trigger so that
the data in the file is not corrupt. Then log the offending program in a
file. Your data stops being corrupted and you know what programs are
causing the problem so they can be fixed. Once all programs are fixed,
remove the trigger since it will cause a minor amount of overhead on
inserts.

This is a great idea when you already know which file has bad data. But in our case, once we know that we can easily fix the problem. What I'd really like to have had is a way to work as it originally did but log an error so that we know which files need fixing. Trying to determine which files MIGHT have bad data is potentially a huge undertaking.

Joe

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.