From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] CREATE TABLE LIKE and SERIAL |
Date: | 2009-11-12 08:00:58 |
Message-ID: | 200911120900.58400.guillaume@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgsql-general |
Le dimanche 1 novembre 2009 à 13:24:10, Dave Page a écrit :
> On Fri, Oct 30, 2009 at 11:12 PM, Guillaume Lelarge
>
> <guillaume(at)lelarge(dot)info> wrote:
> > Le vendredi 30 octobre 2009 à 23:48:45, Tom Lane a écrit :
> >> Thom Brown <thombrown(at)gmail(dot)com> writes:
> >> > How is pgAdmin determining the serial type in this case?
> >>
> >> Most likely it's looking for the pg_depend entry that shows the sequence
> >> as being "owned by" the column. However, that's an oversimplification
> >> of reality. I would imagine that pgAdmin will lie to you in exactly
> >> the same cases that used to break pg_dump (notably, where someone has
> >> manually adjusted either the default expression or the sequence...)
> >
> > I've just read this. I wasn't aware of this. Should we suppress this
> > behavior of pgAdmin?
>
> Do you have a proposed fix? I suspect people won't want us to stop
> showing columns as 'SERIAL' when they actually were created that way.
>
Other ideas than doing what pg_dump does? I'm afraid not.
--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2009-11-12 09:12:00 | Re: [GENERAL] CREATE TABLE LIKE and SERIAL |
Previous Message | svn | 2009-11-11 13:21:33 | SVN Commit by dpage: r8077 - trunk/pgadmin3/pgadmin/schema |
From | Date | Subject | |
---|---|---|---|
Next Message | Ivan Sergio Borgonovo | 2009-11-12 08:13:43 | knowing which table/schema is going to be chosen |
Previous Message | Tatsuo Ishii | 2009-11-12 07:12:30 | pgfoundry new? |