Brian Moon wrote:
The thing about this whole discussion that people seem to miss is that you have to choose to use the IGNORE keyword. We are not talking about default behavior. If you use the IGNORE keyword, you are accepting responsibility for what happens.
What I thought we were discussing was which errors IGNORE ignores. If it ignores totally duplicate records, that's one thing. If it ignores records that violate a constraint like UNIQUE or PRIMARY KEY, that's another. If it can violate one constraint, why not another - throwing out records that have NULLS in NOT NULL fields makes as much sense to me as throwing out those that have duplicate keys. Changing values is another issue - it would be possible, for example, to turn the NULL into a default value or find a new unique value for the PRIMARY KEY / UNIQUE constraint... Cheers, Ann _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
