Ralf Becker wrote: > > Your right that DUAL (system) table seems to be session-dependent. > So everythings fine :-) > > Now I start fighting with updates of LONG columns ;-) > > Ralf >
DUAL is NOT session-dependant. <table_name>.CURRVAL IS session_dependant Elke SAP Labs Berlin > Jean-Michel OLTRA schrieb: > > bonjour, > > > > > > Le mardi 03 ao�t 2004, Ralf Becker a �crit... > > > > > > > >>>SELECT THETABLE.CURRVAL FROM DUAL > >>>and fetch the value. > > > > > >>What happens, if an other concurrent user insert a new row in the > >>meantime? Is this garantied to deliver "my" insert-id? It doesnt look > >>alike to me ... > > > > > > I read that: > > > > The current DEFAULT SERIAL value can be requested using > > <table_name>.CURRVAL where <table_name> is the name of the table that > > contains the column defined as DEFAULT SERIAL. > > For the number generator generated by DEFAULT SERIAL, this is an > > equivalent to the @@IDENTITY or LAST_INSERT_ID() functionality of other > > database systems. > > > > So I "suppose" it's session dependant. > > > > But it is easy to verify with two opened clients. > > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
