Brian Aker wrote:
Do you use the ignore to dump rows? Or do you just want to muddle
through the data? Would it be ok to encourage default values?
The slippery sloap is allowing null on not null columns. I would like to
avoid that, most everything else I am game for.
Personally I use IGNORE to handle loads where I have a primary key and I
just want duplicate data dropped.
A working subquery would have helped... A before trigger will also do
the trick, and that could have made information about the rejected rows
available somewhere else.
Thanks,
Roy
Cheers,
--Brian
On Dec 22, 2008, at 2:05 PM, dormando <[email protected]> wrote:
No, please don't go back into any corner. Discuss, please!
Are you a huge fan of the IGNORE keyword?
-jay
I personally (and my company) use the crap out of it. Along with LOAD
DATA INFILE that was previously discussed. If one or the other goes
away, do we have alternatives?
Think I've used INSERT IGNORE INTO ... SELECT FROM ... a bunch to
collapse data. There isn't really a way to handle bailouts in the
middle, nor is it always reasonable to adjust all of the data first.
ie; You want the constraint on one table but not another, for
different views of the data.
We could potentially get by without using INSERT IGNORE in mogilefs by
handling and ignoring the errors... but bulk requeue attempts would
bail out in the middle, so we'd have to only do one at a time, which
is slow.
-Dormando
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-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
