Re: AW: Re: postgres TODO

> actually, had thought about this too over the weekend ... if I define a
> 'serial' type, it right now creates a sequence for that ... if I recall
> correctly, that was purely a kludge until someone built a better 'serial'
> ...
>
> having an INSERT return the value of 'serial' that was used would save a
> second SELECT call *and* eliminate the requirement for an app programmer
> to have to know to do a 'SELECT curval('table_field_seq');' ...

Yes, I can imagine that the table_field_seq name is kind of flakey. It
will choose a different name if there is a conflict, so it is an chance
for failure.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026