Re: [INTERFACES] locking on database updates
От | Ross J. Reedstrom |
---|---|
Тема | Re: [INTERFACES] locking on database updates |
Дата | |
Msg-id | 19991207111234.A6021@rice.edu обсуждение исходный текст |
Ответ на | RE: [INTERFACES] locking on database updates (Gary Stainburn <gary.stainburn@ringways.co.uk>) |
Ответы |
Re: [INTERFACES] locking on database updates
|
Список | pgsql-interfaces |
On Tue, Dec 07, 1999 at 04:34:37PM -0000, Gary Stainburn wrote: > Hi all, > > I've just read the last message I sent and apologise for the poor English. > Let me put it a little clearer. > > I agree that using a type 'serial' will give me what I want > regarding the key field for my table, and gets round the problem > of concurrent users trying to create records with the same number. > > The problem is that this does not actually give me the number that > was just created. As there is no guarantee that the other fields in > the table are unique (hence the serial field in the first place) I cannot > simply do a select to retrieve it. > > Has anyone any ideas? create table foo (bar serial, baz text); insert into foo (baz) values ('wooble'); select currval('foo_bar_seq'); > > Thanks, > > Gary you're welcome ;-) Ross -- Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu> NSBRI Research Scientist/Programmer Computer and Information Technology Institute Rice University, 6100 S. Main St., Houston, TX 77005
В списке pgsql-interfaces по дате отправления: