I guess technically those don't involve a context switch however they're not exactly the 'pure sql' solution I was half hoping for. However, you got me thinking about the the trigger's performance if a do a bulk insert. Hmmm, I'll have to do some testing, Thanks, Mike On Tue, Jun 7, 2011 at 4:52 PM, David Litchfield <david@xxxxxxxxxxxxxxxxxxxx > wrote: > On 08/06/2011 00:47, David Litchfield wrote: > >> On 08/06/2011 00:12, Michael Moore wrote: >> >>> I think the answer to this is NO, but just to be sure, >>> >>> Is there a single SQL statement that can: >>> >>> 1) SELECT row-X from table A >>> 2) INSERT row-X into table B >>> 3) DELETE row-X from table A >>> >>> It would be nice to be able to do this without a context switch. >>> >> Yes you can... but it requires a bit of trickery (a function that'll >> execute arbitrary sql)... Follow the example below... >> > > Or you could use a trigger to fire after an insert on table_b to delete to > data in table_a... Which is probably the more sane way of doing it, lol :) > > HTH, > David > > -- > //www.freelists.org/webpage/oracle-l > > >