From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: ALTER SEQUENCE: Missing feature? |
Date: | 2004-02-01 20:26:08 |
Message-ID: | 401D60E0.5090404@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>Sequences are tables in some very real senses. I don't see the
>>value in duplicating code just to allow people to spell TABLE as
>>SEQUENCE in these commands...
>>
>>
>
>I guess it comes down to a philosophical thing. Should people need to
>know the PostgreSQL internals like the fact that a SEQUENCE is
>currently implemented as a TABLE, or should they just be able to do
>reasonable things like call ALTER SEQUENCE when they alter a sequence?
>
>
>
I would have to second this. From a user, user space programmer, dba
perspective a SEQUENCE is a
SEQUENCE not a table... thus operations such as ALTER that effect the
SEQUENCE should
use ALTER SEQUENCE.
Sincerely,
Joshua D. Drake
>Cheers,
>D
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-02-01 21:24:18 | Re: ALTER SEQUENCE: Missing feature? |
Previous Message | David Fetter | 2004-02-01 19:57:39 | Re: ALTER SEQUENCE: Missing feature? |