Replacing IDENTITY with lastval()
От | Dmitry Samokhin |
---|---|
Тема | Replacing IDENTITY with lastval() |
Дата | |
Msg-id | E1HjwBJ-000Hnc-00.sdld-mail-ru@f105.mail.ru обсуждение исходный текст |
Ответы |
Re: Replacing IDENTITY with lastval()
Re: Replacing IDENTITY with lastval() |
Список | pgsql-odbc |
Accordind to the release notes, "Use lastval() function to replace IDENTITY on 8.1 or later servers" was introduced in release8.2.0205. This may cause incorrect results: "<...> assumes that your database does not expect any triggers to firewhen the INSERT is executed. If a trigger does fire and if that trigger adds another row to a table, the @@IDENTITY globalvariable would be set to point to that new Identity value—not the one your INSERT generated. <...> work for simplesituations, but not when your database gets more sophisticated". See "Managing an @@IDENTITY Crisis" on MSDN (http://msdn2.microsoft.com/en-us/library/ms971502.aspx) for more details. The PostgreSQL documentation states that the lastval() function returns the value most recently returned by nextval in thecurrent session. It works the same way as the @@IDENTITY variable in MSSQL. The currval(...) function returns a valueof the explicitly specified sequence, this is exactly what we need. Please consider to revert the code. Regards, Dmitry.
В списке pgsql-odbc по дате отправления: