I wrote:
> If I recall the previous discussions correctly there were still some
> gotchas :-(
One point that comes to mind after more thought is that you'd really
like "create table ... default nextval('foo') ..." to understand that
there is a dependency from the column's default expression to seq
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Thu, Sep 22, 2005 at 10:29:21PM -0400, Tom Lane wrote:
>> (wanders off, wondering if a "regclass" literal value would help ...)
> Wouldn't it be easy to create a nextval(oid) function, and have SERIAL
> emit that instead?
Well, for one thing, "nextv
On Thu, Sep 22, 2005 at 10:29:21PM -0400, Tom Lane wrote:
> To my mind the appropriate fix is to come up with some arrangement
> that allows the stored form of NEXTVAL(seq) to specify the referenced
> sequence directly (by OID) rather than as a text string. There are some
> speculations about thi
Tom Lane wrote:
> Bruce Momjian writes:
> > This item has been added to the 8.1 bugs list:
> > http://momjian.postgresql.org/cgi-bin/pgbugs
>
> This isn't going to be fixed for 8.1. I think it's really a variant of
> the TODO item
> o %Have ALTER TABLE RENAME rename SERIAL sequence nam
Bruce Momjian writes:
> This item has been added to the 8.1 bugs list:
> http://momjian.postgresql.org/cgi-bin/pgbugs
This isn't going to be fixed for 8.1. I think it's really a variant of
the TODO item
o %Have ALTER TABLE RENAME rename SERIAL sequence names
To my mind the appropr
This item has been added to the 8.1 bugs list:
http://momjian.postgresql.org/cgi-bin/pgbugs
---
Kouber Saparev wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1883
> Logged by:
The following bug has been logged online:
Bug reference: 1883
Logged by: Kouber Saparev
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux 2.6.11.4
Description:Renaming a schema leaves inconsistent sequence names
Details:
When I renam
