On 9/14/08, Roland Bouman <[EMAIL PROTECTED]> wrote: > > > 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 ....") > > > Agree with Stewart. Batched client protocol. Would be nice too because > it may be easier for the receiving end to shell out the statements to > multiple nodes and execute the batch in parallel.
Actually, it goes a bit beyond batched client protocol. Specifically in an "archiving" context, I'd like to see some kind of functionality like Unix's &&. "Take this record, insert it into this table, and iff that was successful, delete it." (iff=if and only if) -Sheeri
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
