Well, here's thread discussing same problem, and it seems private setId()
should work
http://www.mail-archive.com/user-java@ibatis.apache.org/msg08629.html
Does anyone have any suggestion about this issue? Any input will be
greatly appreciated.
Denis
From: Kezerashvili, Denis
Sent: Thursday, May 08, 2008 12:17 PM
To: user-java@ibatis.apache.org
Subject: Problem exposing protected s
As far as I know you can not do this the way you would think.
I am sure it could be done with two result maps, one for each arm.
Second part is that you will not be able to use .* notation. You will have
to alias the column.
On Fri, May 9, 2008 at 7:29 AM, steve mcdowell <
[EMAIL PROTECTED]> wr
Hi,
When using Hibernate, I have tested the same using rolling back one
session and committing the second one and vice versa. If you observe, The
value u get after the transaction is over will be greater than both the
sequence Id's. That is, if first ones id is X and seconds is X+1, no matter
Argh... sometimes it is that easy.
Yep, two different sql plus sessions, the first will always get *it's*
correct value of sequence.currval, regardless of how many times another
session calls sequence.nextval.
Thanks,
Chris
-Original Message-
From: Clinton Begin [mailto:[EMAIL PROTECTED]
On Fri, May 9, 2008 at 8:12 AM, Chris O'Connell
<[EMAIL PROTECTED]> wrote:
> Thanks. I had never heard this before. Just to make sure we are talking
> about the same thing, I'm not concerned about the sequence returning the
> same value to two different people when the trigger is calling 'nextval
Easy enough to test... open two sqlplus sessions and step through an example...
Clinton
On Fri, May 9, 2008 at 8:12 AM, Chris O'Connell
<[EMAIL PROTECTED]> wrote:
> Thanks. I had never heard this before. Just to make sure we are talking
> about the same thing, I'm not concerned about the seque
Thanks. I had never heard this before. Just to make sure we are talking
about the same thing, I'm not concerned about the sequence returning the
same value to two different people when the trigger is calling 'nextval'.
I'm worried about the fact that two inserts could happen before my code that
t
I have, for example, two tables PERSON, ARM. Lets say that, amongst other
things, PERSON has two columns LEFT_ID and RIGHT_ID, which are references
into the primary key for the ARM table.
My best (wrong) guess is to write something like this:
class Person {
...
Arm left;
Arm right;
}
..
Thanks, it works now :)
cheers
On Thu, May 8, 2008 at 11:23 PM, Christopher Lamey <[EMAIL PROTECTED]>
wrote:
> If you set useStatementNamespaces to 'false', you will not be able to use
> the 'ns.query' notation - you are disabling the feature.
>
> If you set useStatementNamespaces to 'true', you
10 matches
Mail list logo