Re: Transaction control in procedures

2017-11-16 Thread Merlin Moncure
On Thu, Nov 16, 2017 at 12:36 PM, Peter Eisentraut wrote: > On 11/16/17 07:04, legrand legrand wrote: >> We are just opening the "close cursors on/at commit" specification ;o) >> >> - MS SQL server: cursor_close_on_commit >> - Firebird: close_cursors_at_commit >> - DB2: "with hold" syntax >> - ..

Re: Transaction control in procedures

2017-11-16 Thread Peter Eisentraut
On 11/16/17 07:04, legrand legrand wrote: > We are just opening the  "close cursors on/at commit" specification ;o) > > - MS SQL server: cursor_close_on_commit > - Firebird: close_cursors_at_commit > - DB2: "with hold" syntax > - ... > > I think it a plus to support keeping opened cursors at comm

RE: Transaction control in procedures

2017-11-16 Thread legrand legrand
We are just opening the "close cursors on/at commit" specification ;o) - MS SQL server: cursor_close_on_commit - Firebird: close_cursors_at_commit - DB2: "with hold" syntax - ... I think it a plus to support keeping opened cursors at commit time, but impacts have to be checked in details ... Or

Re: Transaction control in procedures

2017-11-15 Thread Peter Eisentraut
On 11/14/17 17:40, legrand legrand wrote: > will that kind of statement (that is permitted with Oracle but gives errors > ora-1555 snapshot too old) be permitted ? > > begin > for c in (select id from tab where cond='blabla') > loop > update tab set x=1 where id=c.id; > commit; > end lo

Re: Transaction control in procedures

2017-11-14 Thread legrand legrand
will that kind of statement (that is permitted with Oracle but gives errors ora-1555 snapshot too old) be permitted ? begin for c in (select id from tab where cond='blabla') loop update tab set x=1 where id=c.id; commit; end loop; end; -- Sent from: http://www.postgresql-archive.o