Re: GetLastInsertID ?
От | Mike Nolan |
---|---|
Тема | Re: GetLastInsertID ? |
Дата | |
Msg-id | 200401042341.i04NfcP3002199@gw.tssi.com обсуждение исходный текст |
Ответ на | Re: GetLastInsertID ? (Doug McNaught <doug@mcnaught.org>) |
Ответы |
Re: GetLastInsertID ?
|
Список | pgsql-general |
> How, exactly, would this happen? Is this worry based on an analysis > of the source code, or just speculation? No, I haven't examined that part of the PG source code. However, I've beta tested software for several decades, and I'm wary of any promises like those proferred for nextval/currval. Besides, Tom has already pointed out one flaw in it, involving persistent connections. (And I could easily see how in a large project team the person writing the nextval/currval code might not know whether or not the connection was persistent.) Could there be others? I'm not willing to bet my application's consistency and data integrity against it. Assuming that there aren't risks or problems with accepted techniques is how most large software projects create flaws. If hackers have done anything positive for software development, it is that they have demonstrated that nearly all memory-based schemes can have overflow problems. -- Mike Nolan
В списке pgsql-general по дате отправления: