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

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