On Wed, Apr 20, 2011 at 7:21 PM, Tim Soderstrom
<[email protected]> wrote:
> 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?

Right. That's why I'm asking for a better way to do bulk updates.
Strict mode is great.

>>> 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? :)

No

> 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.

I'm not asking for naughty things.

> 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.

My app should be easily deployable on a standard webserver. So I can't
depend on non-standard engines.

> 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
>
>
>
>



-- 
Olaf

_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help   : https://help.launchpad.net/ListHelp

Reply via email to