I've primarily seen people use IGNORE in cases when they: (1) were lazy
or (2) didn't have a good mechanism for detecting existing rows and doing updates on them (old code from when ON DUPLICATE KEY UPDATE didn't exist, for example) Jeremy On Mon, Aug 25, 2008 at 12:36 PM, Ann W. Harrison <[EMAIL PROTECTED]> wrote: > > Brian and I had a short off-list discussion that touched on the > IGNORE qualifier and I suggested that Drizzle would be better > without it. In MySQL, IGNORE can qualify a number of different statements > - INSERT, UPDATE, DELETE, REPLACE, CREATE, ALTER ... > > Assuming you're working with real data that you care about, the > most plausible case for ignoring errors is on a load where the > input may not have been carefully screened for duplicates. Even > then few applications can simply ignore errors. My suggestion > was an extension to LOAD that provides an output file where invalid > input can be saved for future examination. > > Is there a plausible (non-QA) use case for ignoring other errors? > > > Cheers, > > > Ann > > > _______________________________________________ > Mailing list: > https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> > Post to : [email protected] > Unsubscribe : > https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
