Nothing to do with ibatis. Look up the error definitions of SQLStates
SQL302 & SQL406 and you will understand why it occurs arbitarily :-)
The value that is trying to be inserted in out-of-range for the column in
the db.
Mario
I personally never trusted the dynamic prepend, so my solution would be to
avoid it;
WHERE 1=1 AND
$logicOperator$ A = #A#
$logicOperator$ B = #B#
-Original Message-
From: Kunle Gbadamosi [mailto:kgbadam...@gmail.com]
Sent: 04 September 2009 12:35 AM
To: user-java@ibatis.apache.
Hi Mario,
Thanks for the reply.
The OS name i5/AS400. One more thing value which I have inserted is
perfectly fine.
As I mentioned sometimes it failed but most of the times it worked.
Please help me out
Mario Briggs wrote:
>
> Nothing to do with ibatis. Look up the error definitions of SQLS
when it succeeds it means u inserted a value which was in the range. When
it fails, u or user was try to insert a value that was not in the required
range.
adi203793
No,
It's not like that,When the sql query failed.
I have tried with same parameter and It worked properly.
As I mentioned earlier I am not able to replicate it.
This was the first and last time query failed while updating and
same case while inserting a record.Next time it inserted properly.
Thes
Based on the proof you have provided (the traces, the SQLSTATES of the
error & spring DAO exception - DataIntegrityViolationException) there is
nothing further you need to look at execpt values being inserted/updated.
SQL0406N A numeric value in the UPDATE or INSERT statement is not
within
On Thu, Sep 3, 2009 at 7:34 AM, Andy Law wrote:
>
> Just to clarify, the xml files don't have to be at the top-level of the
> resources folder. You can impose a directory structure inside the resources
> folder too and so have "the xml files in a directory on their own".
>
Right, I keep mine in
This may have been asked a couple of times, but I haven't seen a useful
answer yet. My domain model has a parent-child relationship, but the child
also needs to have a reference to the parent object. Something like
Group {
int groupId;
String groupName;
List items;
.
A stack overflow is most likely a bug in iBATIS. Can you create a simple
unit test (HSQLDB or Derby/JavaDB) and create a Jira ticket for it?
I believe we have unit tests to cover this case, but your code must test the
framework in a new way.
Thanks much.
Clinton
On Fri, Sep 4, 2009 at 12:43 PM
PS: Please include the exception as well.
Clinton
On Fri, Sep 4, 2009 at 2:05 PM, Clinton Begin wrote:
> A stack overflow is most likely a bug in iBATIS. Can you create a simple
> unit test (HSQLDB or Derby/JavaDB) and create a Jira ticket for it?
>
> I believe we have unit tests to cover this
10 matches
Mail list logo
