From: | "Dave Page" <dpage(at)postgresql(dot)org> |
---|---|
To: | "Andy Shellam" <andy(dot)shellam-lists(at)mailnetwork(dot)co(dot)uk> |
Cc: | "Guillaume Lelarge" <guillaume(at)lelarge(dot)info>, pgadmin-support(at)postgresql(dot)org |
Subject: | Re: New sequence in 1.8.1 |
Date: | 2008-01-15 09:38:01 |
Message-ID: | 937d27e10801150138k42102fcbm9cadf6808ef226df@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On 14/01/2008, Andy Shellam <andy(dot)shellam-lists(at)mailnetwork(dot)co(dot)uk> wrote:
> Hi Dave,
>
> I see your point about it not doing anything after the column is created, as
> a serial column is just an integer column with a new default value. I liked
> the idea of being able to specify a different sequence to use with the
> serial column, but having said that I can't think of many uses where you'd
> want to!
>
> Unless you can make the sequence combo of any use (e.g. to change the
> default sequence used when creating the column) I'd say get rid of it!
Thanks Andy. Any more opinions before I start pulling code?
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2008-01-15 10:28:26 | Re: New sequence in 1.8.1 |
Previous Message | Dave Page | 2008-01-15 08:52:18 | Re: Show NULL values AS <NULL> not working |