Re: nextval/dbi question
От | harrold@sage.che.pitt.edu |
---|---|
Тема | Re: nextval/dbi question |
Дата | |
Msg-id | Pine.LNX.4.21.0108051905050.18298-100000@sage.che.pitt.edu обсуждение исходный текст |
Ответ на | Re: nextval/dbi question (Horst Herb <hherb@malleenet.net.au>) |
Список | pgsql-novice |
john There is no operating system but linux and linus is its kernel maintainer. Sometime in August Horst Herb assaulted keyboard and produced... |On Monday 06 August 2001 08:47, harrold@sage.che.pitt.edu wrote: | |> i was under the impression that nextval would give what the nextval would |> be. i didnt think it was suppose to increment it. after reading your |> response and someone else's it seems i need to get the next value of the |> key and insert it explicitly is that correct? | |Yes. Alternatively, you can let Postgres use nextval implicitly, and call |currval afterwards to get the value of the inserted "nextval" | thanks. one more question. what can i do to prevent another insert from taking place before the currval request is made? is this even an issue aslong as the currval query is executed using the same connection? john
В списке pgsql-novice по дате отправления: