On 12/22/08 3:57 PM, Jay Pipes wrote:
Brian Moon wrote:
This would likely mean the dropping of the IGNORE keyword from Drizzle's
SQL syntax.
Standards are for breaking. Or is that rules? Really, it *feels* like
Drizzle is becoming more about making an SQL standards compliant DBS
than one that is fast, maintainable and good for scale out. I
understand wanting to have known expectations. But, I have just seen
"we should do x because it is the standard" thrown around a lot
lately. Whereas, when Drizzle started, the tone was more to use the
standard where the standard made sense and not use it when it did not
make sense. Maybe it does make sense in this case, but, I just don't
see the discussion happening these days.
Ok, back to my corner.
No, please don't go back into any corner. Discuss, please!
Are you a huge fan of the IGNORE keyword?
I am a bigger fan of DELAYED. But I do use IGNORE on a regular basis
for mostly bulk inserts.
Looking through my code, one place I do use it is in triggers. We have
a job queue table that is inserted into via triggers when data changes
in several tables. To avoid issues with multiple triggers, I use IGNORE
on the inserts. That is a fairly niche problem and perhaps there is
another way. But, IGNORE exists so I use it.
But, that was just the trigger that kind of got me thinking about where
Drizzle is going in terms of SQL standards vs. scale out computing. And
I am not blaming or trying to be a flame tard. I respect everyone on
this list. And I am very excited about Drizzle and its future.
--
Brian Moon
Senior Web Engineer
------------------------------
When you care enough to spend the very least.
http://dealnews.com/
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
