From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Dickson S(dot) Guedes" <listas(at)guedesoft(dot)net>, pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Renaming sequence auto generated by SERIAL type don't update pg_attrdef |
Date: | 2009-03-10 03:44:08 |
Message-ID: | 49B5E208.1080205@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Tom Lane wrote:
> "Dickson S. Guedes" <listas(at)guedesoft(dot)net> writes:
>> Shouldn't the JDBC driver use another query instead that, since docs
>> alerts[1] to this problem?
>
> What's the default value being used for anyway? If it's to determine
> which sequence is associated with the column, I think you shouldn't be
> looking at pg_attrdef at all; you should look for a dependent sequence
> via pg_depend. But maybe it's only being used to check if the column
> has a default, in which case the possible staleness of the string
> value isn't important.
I'm guessing that particular query is from
DatabaseMetaData.getColumns(), which returns amongst other things:
13. COLUMN_DEF String => default value (may be null)
(yes, that's the sum total of the JDBC documentation about that piece of
metadata)
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-03-10 03:54:08 | Re: Renaming sequence auto generated by SERIAL type don't update pg_attrdef |
Previous Message | Scott Carey | 2009-03-10 03:38:50 | Re: [PERFORM] Query much slower when run from postgres function |