Re: GetLastInsertID ?
От | Doug McNaught |
---|---|
Тема | Re: GetLastInsertID ? |
Дата | |
Msg-id | 87smiv8ge9.fsf@asmodeus.mcnaught.org обсуждение исходный текст |
Ответ на | Re: GetLastInsertID ? (Mike Nolan <nolan@gw.tssi.com>) |
Ответы |
Re: GetLastInsertID ?
Re: GetLastInsertID ? |
Список | pgsql-general |
Mike Nolan <nolan@gw.tssi.com> writes: > It sound to me like there's the potential for a second web program sharing > the persistent connection to do something in between the nextval and > the currval. "Don't do that then." Your code should hang on to the same connection for as long as it needs to rely on the correct value of currval(). > Is currval for each process maintained at the front end (e.g., the PHP or > psql connection) or at the back end? If the latter, isn't there always > the potential for memory overflows or other high-demand situations causing > the pairing of nextval/currval to get corrupted or lost, in which case > RELYING upon it for the last key value could be a source of problems. How, exactly, would this happen? Is this worry based on an analysis of the source code, or just speculation? -Doug
В списке pgsql-general по дате отправления: