Обсуждение: Re: Why fields order is wrong ?

------------- Begin Forwarded Message -------------

Date: Tue, 11 Apr 2000 10:58:50 +1000
From: Joe Shevland <shevlandj@kpi.com.au>
Subject: Re: Why fields order is wrong ?
To: EJBoss <ejboss@list.working-dogs.com>
MIME-version: 1.0
Content-transfer-encoding: 7bit
X-Accept-Language: en
List-Subscribe: <mailto:ejboss-on@list.working-dogs.com>
List-Digest: <mailto:ejboss-digest@list.working-dogs.com>
List-Unsubscribe: <mailto:ejboss-off@list.working-dogs.com>
List-Software: LetterRip Pro 3.0.7 by Fog City Software, Inc.

Might be best to CC this to the Postgres Interfaces
mailing list (pgsql-interfaces@postgresql.org), as Peter
Mount (the guy behind the JDBC driver) has some code that
he's waiting to unleash that'll help us out a lot with these
bugs (and may have possible workarounds in the interim). I'd
do it but don't have any time to follow it up.

Regards,
Joe


Paolo Sommaruga wrote:
> 
> >Date: Mon, 10 Apr 2000 08:52:56 -0700
> >From: marc fleury <marc.fleury@telkel.com>
> >Subject: Re: Why fields order is wrong ?
> >To: EJBoss <ejboss@list.working-dogs.com>
> >MIME-version: 1.0
> >Content-transfer-encoding: 7bit
> >X-Accept-Language: en
> >List-Subscribe: <mailto:ejboss-on@list.working-dogs.com>
> >List-Digest: <mailto:ejboss-digest@list.working-dogs.com>
> >List-Unsubscribe: <mailto:ejboss-off@list.working-dogs.com>
> >List-Software: LetterRip Pro 3.0.7 by Fog City Software, Inc.
> >
> >I am still a bit fuzzy on this.
> >
> >Do we need to fix it? If so how, we use a linked structure?
> >
> >(I actually might be able to secure a couple of hours on the code this
> >week, the CTO thing is taking way to much time of my coding :(
> >
> >marc
> 
> I have tried the Damon patch but the problem stays.
> I have verified that the Postgres 7.0 beta3 works good If one insert manually 
in
> psql the syntax which EJBoss calls
> 
> [sql] executing statement  INSERT INTO Books ( title, discount, authors, 
price,
> code )
>         VALUES  (  ? ,  ? ,  ? ,  ? ,  ?  )
> 
> but with EJBoss there is the Exception
> 
> [Exception]
> java.lang.NullPointerException
>         at postgresql.util.PSQLException.translate(PSQLException.java:76)
>         at postgresql.util.PSQLException.<init>(PSQLException.java:45)
>         at postgresql.fastpath.Fastpath.fastpath(Compiled Code)
> ....
> 
>                         Paolo Sommaruga
> 
> 
> --
> --------------------------------------------------------------
> To subscribe:        ejboss-on@list.working-dogs.com
> To unsubscribe:      ejboss-off@list.working-dogs.com
> Problems?:           jon@working-dogs.com

-- 
Joe Shevland
Principal Consultant
KPI Logistics Pty Ltd
http://www.kpi.com.au
mailto:shevlandj@kpi.com.au


--
--------------------------------------------------------------
To subscribe:        ejboss-on@list.working-dogs.com
To unsubscribe:      ejboss-off@list.working-dogs.com
Problems?:           jon@working-dogs.com


------------- End Forwarded Message -------------

In short, a statement like:

INSERT INTO Vehicles ( RegID, Owner ) VALUES ( 'DA1111', 'Bill' )

works from the psql CLI, but not through JDBC using PostgreSQL
7.0 beta 3 and prepared statements. Does this look like a
version conflict with the JDBC drivers (is it worth compiling
the ones that come with the beta again, I *think* they may
still be using the 6.5.3/Java2 drivers.

Cheers,
Joe

Paolo Sommaruga wrote:
> 
> ------------- Begin Forwarded Message -------------
> 
[snipped]
> > I have verified that the Postgres 7.0 beta3 works good If one insert manually
> in
> > psql the syntax which EJBoss calls
> >
> > [sql] executing statement  INSERT INTO Books ( title, discount, authors,
> price,
> > code )
> >         VALUES  (  ? ,  ? ,  ? ,  ? ,  ?  )
> >
> > but with EJBoss there is the Exception
> >
> > [Exception]
> > java.lang.NullPointerException
> >         at postgresql.util.PSQLException.translate(PSQLException.java:76)
> >         at postgresql.util.PSQLException.<init>(PSQLException.java:45)
> >         at postgresql.fastpath.Fastpath.fastpath(Compiled Code)
> > ....
> >
> >                         Paolo Sommaruga
[snipped]