db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zsolt Koppany" <zkoppanyl...@intland.com>
Subject RE: Derby 10.3.1.4 not working with ibatis-2.3.0.677
Date Sat, 08 Sep 2007 19:13:12 GMT
Larry,

thank you but it means form me approx. 400 statements.

Zsolt

Zsolt 
> -----Original Message-----
> From: larry.meadors@gmail.com [mailto:larry.meadors@gmail.com] On Behalf
> Of Larry Meadors
> Sent: Saturday, September 08, 2007 4:43 PM
> To: user-java@ibatis.apache.org
> Cc: Derby Discussion
> Subject: Re: Derby 10.3.1.4 not working with ibatis-2.3.0.677
> 
> Actually, you can tell iBATIS the type (see page 29 in the user guide)
> - in an insert or update, user the following notation:
> 
> #property:JDBCTYPE#
> 
> You can get a list of the valid JDBC types here:
> 
> http://java.sun.com/j2se/1.5.0/docs/api/java/sql/Types.html
> 
> So if your property is named address, and the type is VARCHAR it would
> be #address:VARCHAR#.
> 
> Larry
> 
> 
> On 9/8/07, Zsolt Koppany <zkoppanylist@intland.com> wrote:
> > Knut,
> >
> > thank you fort he info, but not my application but ibatis uses jdbc code
> and
> > I cannot do anything about.
> >
> > Our application does work with oracle-10, oracle-9, mysql-4, mysql-5 and
> > derby 10.2.2.0 and we have this problem only with derby 10.3.1.4.
> >
> > We cannot modify ibatis. Is that possible to get a derby-client that
> works
> > as before or we cannot use derby in the future?
> >
> > Zsolt
> > > -----Original Message-----
> > > From: Knut.Hatlen@Sun.COM [mailto:Knut.Hatlen@Sun.COM]
> > > Sent: Friday, September 07, 2007 9:16 AM
> > > To: Derby Discussion
> > > Subject: Re: Derby 10.3.1.4 not working with ibatis-2.3.0.677
> > >
> > > Zsolt Koppany <zkoppanylist@intland.com> writes:
> > >
> > > > Hi,
> > > >
> > > > I tried to upgrade to derby 10.3.1.4 but I get strange error
> messages
> > > that I
> > > > didn't get with derby 10.2.2.0.
> > > >
> > > > I use 10.3.1.4 with ibatis-2.3.0.677.
> > > >
> > > > Any ideas?
> > > [...]
> > > > --- Cause: java.sql.SQLException: An attempt was made to get a data
> > > value of
> > > > type '<UNKNOWN>' from a data value of type 'VARCHAR'.
> > > [...]
> > > >     at org.apache.derby.client.am.PreparedStatement.setNull(Unknown
> > > Source)
> > >
> > > Hi,
> > >
> > > It seems like your application calls PreparedStatement.setNull() with
> an
> > > invalid type specification. If you change the type to
> > > java.sql.Types.VARCHAR, it will probably work. This was changed in
> > > 10.3.1.4 to make the network client driver and the embedded driver
> > > behave the same way. Please see this section in the release notes for
> > > details:
> > >
> > > http://db.apache.org/derby/releases/release-10.3.1.4.cgi#N10C87
> > >
> > > --
> > > Knut Anders
> >
> >


Mime
View raw message