On Fri, Jun 27, 2003 at 10:45:07 +0200, Dani Oderbolz <oderbolz@ecologic.de> wrote:
>
> Yea, fine, but I propose a different (deeper) approach.
> Why does SERIAL only enforce a DEFAULT?
Because it is faster.
> This is not an exact imitation of an autoincrement, as a DEFAULT can be
> overwritten.
There are probably other differences as well, since serial only provides
a way to get unique values. If you want more meaning than that you
have to be careful.
> In my oppinion, SERIAL should implicitly create a Trigger on the table,
> which then
> handles this transparently.
> Would that be difficult?
It shouldn't be too difficult to write some triggers that make something
closer to autoincrement. It probably won't work very well if there are
lots of concurrent updates though. You can either lock the table with
the column exclusively and then find the largest value and then use
that value plus one. Don't use max for this. Make an index on the
autoincrement column and use order by and limit 1 to get the largest
value. The other option is to keep the sequence value in other table.
You can use select for update to update it. You will want to vacuum
this table often enough that it will stay on one page.
> (I am already writing a Procedure which gets all the info needed out of
> the Catalog,
> but my problem is that I need some dynamic statements in there...)
>
> Cheers, Dani
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend