Baron Schwartz wrote:
What other things are hard for MySQL now, and are just kinda hard to do purely because relational-ism makes it so? Some places where MySQL has broken relational-ism, like ON DUPLICATE KEY UPDATE, have really been beneficial -- more?
I would argue this does not break relational-ism. It is just a pragmatic way to resolve a constraint violation.
How about inserting and getting the result back at the same time? (Postgres does this already) Or inserting into two tables at once? Or deleting from one table and inserting into another at the same time? Or deleting while getting back the deleted rows? (That would be a "queue", but it would be useful for a lot more than that -- think data archiving -- DELECT FROM foo INTO foo_archive WHERE ....")
An alternative to defining more complicated SQL statements may be to create procedures and triggers that perform these actions - without sacrificing performance.
Roy _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
