Hey Bryan,
Thanks for your help. Yes I am using hibernate and I'm fairly certain that it
does have something do with what is happening at the hibernate level as I tried
updating to the later version of hibernate 3.5.1-Final and ran into a very
different error but the issue with prepared stateme
I agree. This is not a Derby error. Derby is just throwing the error
because Hibernate, in this case, is trying to get a 3rd parameter when there
are only two in the query. Check that the (Hibernate) dialect is configured
for Derby, and then ask this over on the Hibernate forums.
You can also e
This part:
> where product0_.lid=? and product0_.userVersion=? fetch first 2 rows
seems to match this part:
> cq.where(cb.and(cb.equal(lidAttr, lid), cb.equal(userVersionAttr,
userVersion)));
pretty closely, so it's hard to imagine why your O/R tool thought it
needed to set 3 parameters in th
Hey Bryan,
Thanks for the tip. From the derby.log that got created I can see that the
following is logged:
2010-05-26 04:23:06.228 GMT Thread[http-8080-1,5,main] (XID = 313), (SESSIONID
= 4), (DATABASE = RegistryDB), (DRDAID = null), Committing
2010-05-26 04:23:06.229 GMT Thread[http-8080-1,5,m
Caused by: ERROR XCL13: The parameter position '3' is out of range. The
number of parameters for this prepared statement is '2'.
...
Any direction or feedback as to where I should look to resolve this
issue would be greatly appreciated. If more detail is needed such as a
I'm not sure where t
Hi All,
I'm not quite certain this is where I should be sending this message but I'm at
a loss as to what the cause of my error is and at the base it seems to be
coming from Derby.
I've encountered a strange issue when using Derby as my data store in
conjunction with JPA 2.0. I'm a novice and
