> Yeah, you could just keep using MySQL. If it works with what you have, why > change it? > > -Sheeri > > (I use IGNORE all the time, but again, IGNORE is specifically and > consciously saying "I know there might be problems with duplicate keys, but > I'm choosing to ignore it. Unintentional data loss=bad, intentional data > loss = your own problem :) )
I'm trying to avoid excuses from rolling out drizzle ;) The pattern is useful enough that I don't really see the reason to remove it. I /do/ like the ideas on making it more flexible, as well as looking at the queue functionality/etc. Basically, if I have projects I can port to drizzle and have them still be fast, it'll be good for the projet for me to pipe up when potential issues arise :) As-is our postgres port for mogilefs is slow, and breaks some of the locking mechanics in both the mysql and postgres implementations. Maybe someone with more awesome postgres-fu could get it up to date, but the INSERT IGNORE loss was one of the big performance drops. -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
