Sheeri, at the rate with which you give away first borns, you don't NEED
a pony!
Sheeri K. Cabral wrote:
On 9/14/08, *Stewart Smith* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
On Sun, Sep 14, 2008 at 11:30:53AM -0400, Sheeri K. Cabral wrote:
> 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)
Could be solved with a "stop on error" flag to the batch? (or per
command).
Preferably on the "row" level, with an output of the primary keys on
the rows it couldn't delete.
And a pony, please. (actually, they cost too much, I don't really
want a pony).
That's a specific case, and perhaps this is more of a procedural,
cursor-level operation -- "if this row fails, note it an move on"
which is of course a plugin-type idea
A relational language isn't designed for things like archiving old
stuff, because the relational theory doesn't have any say as to the
implementation -- it's the implementation of SQL brings us to "big
tables take a long time to search through, and that's unacceptable to
us humans".
So, um, yeah. probably best left to a plugin, stored
procedure-with-a-cursor type thing.
-Sheeri K. Cabral
------------------------------------------------------------------------
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
