Re: Strange behaviour of JDBC driver for PostgreSQL

Try issuing a "SELECT VERSION()" on the DB that
DatabaseMetaData.getDatabaseProductVersion reports as being 6.5.2, and
see what gives.

On Tue, 2002-12-17 at 17:50, Carlos Correia wrote:
> Dave Cramer wrote:
>
> >Carlos,
> >
> >Sorry, I didn't read your email carefully enough. The driver won't work
> >with a 6.5.2 database, my apologies. You will need to upgrade the remote
> >server
> >
> >Dave
> >
> >On Tue, 2002-12-17 at 12:54, Carlos Correia wrote:
> >
> >
> >>I have problems with PostgreSQL when connecting from another machine in
> >>the same network, after upgrading to 7.2.2 (Mandrake 9.0).
> >>
> >>When invoking 'getColumns()' on a DatabaseMetaData object I get (very)
> >>different results when I invoke it in the local machine (in which works
> >>good) then when I invoke it in another machine in the network as you can
> >>see below:
> >>
> >>I've made a small Java class to reproduce its bizarre behaviour (I'm
> >>using the same driver in both machines -
> >>/usr/share/pgsql/jdbc7.2dev-1.2.jar from Mandrake 9.0), here is its output:
> >>
> >>

<snip>

> >>
> >>
> The information that is correct is the one from the localhost (version
> 7.2.2)
> I've never used such a version (6.x.x).
>
> I've downloaded the 7.3 driver (pg73jdbc3.jar) and... It happened the
> same (even with the same line numbers in the SQLException's stack
> trace). I'm sure I made no mistake!
> Note: I'm also sure there are no more Postgres installations in the
> network.
>
> Carlos Correia

--
[]'s
Daniel Serodio