Skip site navigation (1) Skip section navigation (2)

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

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Kris Jurka <books(at)ejurka(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-03-31 12:13:03
Message-ID: 49D208CF.3020606@opencloud.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
Kris Jurka wrote:
> 
> 
> On Mon, 20 Apr 2009, j.random.programmer wrote:
> 
>> While using JDBC MetaData for my O/R tool, I've come across this
>> bug recently;
>>
>> When getting JDBC Meta data, the column numbers for the
>> following 2 columns, via ('ORDINAL_POSITION') of the 2
>> columns are IDENTICAL:
>>
>> [1]
>> colname=dictname, colnum=1, sqltype=12, typename=name, 
>> colsize=2147483647, nullable=false, isAutoIncrement=false, 
>> remarks=null, hasRemarks=false, isPK=false, fkdata=null]
>>  --and--
>> [2]
>> colname=dict_name, colnum=1, sqltype=12, typename=text, 
>> colsize=2147483647, nullable=false, isAutoIncrement=false, 
>> remarks=null, hasRemarks=false, isPK=false, fkdata=null]
>> -------------------------------------------------------------
>>
>> Note, "dict_name" does not show up via the \d pg_ts_dict
>> output above but this, possibly extraneous column, does
>> show up in the JDBC MetaData.
> 
> Without showing the calls you're making it's not completely clear what 
> your ORM tool is doing.  The attached test case of just getColumns has 
> no problems.

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

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

-O

In response to

Responses

pgsql-jdbc by date

Next:From: Scott MurphyDate: 2009-04-03 18:59:40
Subject: autogenerated keys is not supported in 8.4dev-700 as specified in the changelog
Previous:From: Oliver JowettDate: 2009-03-31 08:31:34
Subject: Re: Problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group