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

Re: Bug in metadata.getColumns()/ORDINAL_POSITION

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "j(dot)random(dot)programmer" <javadesigner(at)yahoo(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Bug in metadata.getColumns()/ORDINAL_POSITION
Date: 2007-02-17 20:01:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
"j.random.programmer" <javadesigner(at)yahoo(dot)com> writes:
> This is a quick followup to my earlier post. Upon
> further 
> testing, this bug reliably and reproducably happens 
> when an "alter table" command is used on the database.

So the problem is that it's returning pg_attribute.attnum without any
consideration for earlier dropped columns.  Not sure how expensive it'd
be to get the current logical column number, though --- at a minimum one
would have to select all the table's pg_attribute rows :-(

			regards, tom lane

In response to


pgsql-jdbc by date

Next:From: santosh dwivediDate: 2007-02-17 20:45:16
Subject: unsubscribe
Previous:From: j.random.programmerDate: 2007-02-17 19:17:41
Subject: Re: Bug in metadata.getColumns()/ORDINAL_POSITION

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