On Mon, Feb 26, 2007 at 11:14:01PM -0500, Tom Lane wrote: > Rusty Conover <[EMAIL PROTECTED]> writes: > > I didn't see this on the TODO list, but if it is my apologies. Is it > > in the cards to expand the functionality of DELETE/UPDATE returning > > to be able to sort the output of the rows returned? > > No. > > > Or allow delete > > and update to be used in sub-queries? > > That's been discussed but the implementation effort seems far from > trivial. One big problem is that a sub-query can normally be > re-executed multiple times, eg on the inner side of a join; whereas > that's clearly not acceptable for an insert/update/delete.
Couldn't we avoid that by writing the data to a tuplestore? Or is it too hard to detect the cases when that would need to happen? -- Jim Nasby [EMAIL PROTECTED] EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
