On Apr 20, 2011, at 12:10 PM, Olaf van der Spek wrote: > On Wed, Apr 20, 2011 at 4:24 PM, Tim Soderstrom > <[email protected]> wrote: >>> I'd prefer a solution that's as simple as the original. >> >> Well, I mean, then use MySQL :) > > I am. But even in MySQL this usage conflicts with strict mode.
Right, so...if you're using strict mode and running into issues, that tells me that you are using things that obviously don't work in strict mode. Isn't the whole point of strict mode that it's more strict, predictable, and has the absence of assumption? > >> Those features were removed from Drizzle for a reason (and probably a very >> good one) > > Probably? IMO (bulk) data updates should be a first class citizen of a DBMS. First class might be a bit much but otherwise agreed. Having ways to update data fast is a good thing, but it's not the most important thing for an RDBMS. If you want fast updates, I hear there's this thing called MongoDB. It's Web-Scale! :) (yeah, I was fanning the flames just a little there). > >> but if you're application doesn't fit and you're not willing to modify it, >> then I would suggest you use something that fits your requirements. > > I'd rather modify Drizzle. :p Hah, I assume that's in jest? :) You'd rather modify Drizzle than fixing your app? That's like replacing the spark plugs in your engine when you have a flat tire :) To be fair, one of the goals of Drizzle as far as I am aware is speed - but not at the expense of allowing naughty things. MySQL's SQL_MODE is one terrible example of what happens when you allow assumptions within the database so don't expect Drizzle to likely add in anything that would allow poorly designed databases and/or apps to get away with things that they should have been able to get away with in the first place. What you will have in Drizzle (or should, I should say) is clean methods of doing a large amount of things. I think in your case looking at some of the No-SQL like options in Drizzle may be your best bet if you need very high UPDATE performance subject to the limitations of InnoDB anyway. PBXT fell out of the Drizzle tree :( but you could try BlitzDB (I think that's still in there?). There's the commercial solutions from the likes of TokuTek as well but I don't think they have a way to integrate into Drizzle at the moment. Something to consider if you need fast performance from an RDBMS. By the way, I'm in NO way trying to suggest your application is badly written - that's not my point at all. Most of these suggestions are generic to how to solve things like sql_mode issues (or more specifically strictness in general) and how to do fast updates in Drizzle (with a minor poke at MongoDB) :) Tim _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
