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

Re: Strange behaviour of JDBC driver for PostgreSQL

From: Dave Cramer <Dave(at)micro-automation(dot)net>
To: Carlos Correia <carlos(at)m16e(dot)com>
Cc: "Thomas O'Dowd" <tom(at)nooper(dot)com>,"pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Strange behaviour of JDBC driver for PostgreSQL
Date: 2002-12-19 11:42:36
Message-ID: 1040298156.16014.358.camel@inspiron.cramers (view raw or flat)
Thread:
Lists: pgsql-jdbc
Carlos,

Ok, so the question becomes what database did the driver connect to? I
can assure you it has no version information inside it so it must have
received that from somewhere? Also the fact the the driver behaves
differently when connected remotely suggests something is wrong.

so what did you input for the -h parameter below?

also can you write a java program that first gets the connection, and
then waits for input, then in another terminal session do a netstat -nlp
| grep 5432 

Dave
On Thu, 2002-12-19 at 06:20, Carlos Correia wrote:
> I've been working with Linux and Java for more then 4 years, so I'm sure 
> of what I'm saying: never had or used such a version!
> 
> Anyway, here's the output from:
> 
> $ psql -h REMOTEHOSTNAME -U USERNAME -c 'SELECT version();' DBNAME
> 
> 
>                                               
> version                                              
> ----------------------------------------------------------------------------------------------------
>  PostgreSQL 7.2.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2 
> (Mandrake Linux 9.0 3.2-1mdk)
> (1 row)
> 
> Best Regards,
> 
> Carlos
> 
> Thomas O'Dowd wrote:
> 
> >Carlos,
> >
> >To satisfy everyones curiosity why don't you try sending us the output
> >of the following command from your local machine...
> >
> >$ psql -h REMOTEHOSTNAME -U USERNAME -c 'SELECT version();' DBNAME
> >
> >This will access the remote database DBNAME in much the same way as the
> >driver does.
> >
> >Tom.
> >
> >On Thu, 2002-12-19 at 02:55, Carlos Correia wrote:
> >  
> >
> >>Fernando,
> >>
> >>i am sure the db is version 7.2.2
> >>
> >>Thanks anyway,
> >>
> >>Carlos
> >>
> >>Fernando Nasser wrote:
> >>
> >>    
> >>
> >>>Carlos Correia wrote:
> >>>
> >>>      
> >>>
> >>>>Dave Cramer wrote:
> >>>>
> >>>>        
> >>>>
> >>>>>Carlos,
> >>>>>
> >>>>>Is this a new message today, or one from yesterday?
> >>>>> 
> >>>>>
> >>>>>          
> >>>>>
> >>>>Dave,
> >>>>
> >>>>It is the same messge, but as I think that everyone is 
> >>>>misunderstooding the problem, I'll try to resume it:
> >>>>
> >>>>1. I don't know why the driver reports version 6.5.2, as I don't have 
> >>>>such a version.
> >>>>        
> >>>>
> >>>The JDBC driver receives the version from the database backend when 
> >>>connecting and that is what is printed by the 
> >>>getDatabaseProductVersion() function.  There is no way it can generate 
> >>>a 6.x.x version number by itself.
> >>>
> >>>You _must_ be connecting to a 6.5.2 backend.
> >>>
> >>>
> >>>      
> >>>
> >>
> >>---------------------------(end of broadcast)---------------------------
> >>TIP 2: you can get off all lists at once with the unregister command
> >>    (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
> >>    
> >>
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
> http://archives.postgresql.org
-- 
Dave Cramer <Dave(at)micro-automation(dot)net>


In response to

Responses

pgsql-jdbc by date

Next:From: Carlos CorreiaDate: 2002-12-19 12:41:01
Subject: Re: Strange behaviour of JDBC driver for PostgreSQL
Previous:From: Dave CramerDate: 2002-12-19 11:37:17
Subject: Re: error when using move, any suggestions?

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