Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)

From: Kris Jurka <books(at)ejurka(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: "j(dot)random(dot)programmer" <javadesigner(at)yahoo(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)
Date: 2009-04-21 07:07:31
Message-ID: Pine.BSO.4.64.0904210305250.29926@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Wed, 1 Apr 2009, Oliver Jowett wrote:

> I wonder if this is a problem with dropped columns again.
>

I doubt it, dropped columns never have a duplicate pg_attribute.attnum
column. If he somehow managed to get two columns with the same name but
different number that might be a possibility, but he's got two columns
with the same number but different names.

> (mr. random programmer, please tell us your JDBC driver version and
> postgresql server version at least!)
>

He did mention these in his original email, I just trimmed it out.

Kris Jurka

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message j.random.programmer 2009-04-21 07:19:23 Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)
Previous Message Kris Jurka 2009-04-21 06:37:04 Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)