From: | Joachim Wieland <joe(at)mcknight(dot)de> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, nikolay(at)samokhvalov(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] Sequences/defaults and pg_dump |
Date: | 2006-02-09 19:31:07 |
Message-ID: | 20060209193107.GA4265@mcknight.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Wed, Feb 08, 2006 at 10:57:20PM -0500, Bruce Momjian wrote:
> > > > > TODO has:
> > > > > * %Disallow changing default expression of a SERIAL column
> > Sure, the "DROP SERIAL" I proposed would rather "change" the data type
> > to int by dropping the default and would delete referring pg_depend entries.
> > Read it more as a kind of "drop autoincrement functionality for this
> > column".
> > The problem I see (but you might see it differently) is that you can't drop
> > this autoincrement stuff without also dropping the column once you forbid to
> > change the default (yeah I know, changing the default is even worse and
> > leaves you with incorrect dependencies).
> I assume an ALTER COLUMN ... TYPE INTEGER would drop the SERIAL part.
So far it doesn't because it doesn't know the difference between serial
and int.
What about this proposal for serial columns:
- DROP DEFAULT drops serial and removes dependencies
- SET DEFAULT forbidden, issues a hint to DROP DEFAULT first
Is it also desired to convert an int column to a serial column?
(moving to -hackers)
Joachim
--
Joachim Wieland joe(at)mcknight(dot)de
C/ Usandizaga 12 1°B ICQ: 37225940
20002 Donostia / San Sebastian (Spain) GPG key available
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2006-02-09 19:38:11 | Re: What's faster? |
Previous Message | Benjamin Arai | 2006-02-09 19:23:55 | Return more then one value using PL |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2006-02-09 19:31:48 | Re: PostgreSQL 8.0.6 crash |
Previous Message | Stephen Frost | 2006-02-09 19:17:20 | Re: PostgreSQL 8.0.6 crash |