Just thought to post the complete configuration of dao.xml and
sql-map-config..
dao.xml
sql-map-config.xml
===
mfs wrote:
>
> Ok, well these would sound funny, but i didn't knew at al
Thanks for the quick followup Larry
I think i need to give some more details here...
I have already OracleAs (Oc4j) connection pooling setup, and the jndi
datasource (jdbc/proxy) is already configured to use the very connection
pool.
Anyways, last night while trying to test as to what the
I'm re-reading your questions to make sure I understand. To clarify my
previous answer, if all you have is the primary key of the object you want
to update, then you would need to perform two queries:
SELECT ID, TIMESTAMP
...edit...
UPDATE WHERE ID AND TIMESTAMP
If you can maintain the ID and th
Your fundamental question is obviously unclear. Thus repeating your
fundamental question is not helpful. Clearly our fundamental answers are
inadequate or are being fundamentally misunderstood. Fundamentally, this is
simple for everyone else who has ever achieved optimistic locking with
iBATIS,
Hi,
Do you feel it would be difficult to persist the "Old Object". I am not
sure if you are confusing yourself with Ibatis thinking if it will work like
Hibernate. The way of saying "Old Object" Seems to remind me of just that.
If thats the case, I dont think Ibatis needs you to have the Old "
My fundamental question was:
Is there a way to achieve optimistic locking, if the "OldObject" and/or the
update timestamp of the old object were NOT available in scope.
It seems that the solution in iBATIS requires you to keep the "OldObject" in
scope because, the where clause requires you to p
I shouldn't even call it "old id"... it's "the id".
On Thu, Oct 9, 2008 at 8:04 AM, Clinton Begin <[EMAIL PROTECTED]>wrote:
> You don't need the exact OldObject instance. You just need the ID.
> There's no magic there... you simply cannot update the database record
> without the old id...
>
> C
You don't need the exact OldObject instance. You just need the ID. There's
no magic there... you simply cannot update the database record without the
old id...
Clinton
On Thu, Oct 9, 2008 at 7:57 AM, mule_user <[EMAIL PROTECTED]> wrote:
>
> My fundamental question was:
>
> Is there a way to ac
Greetings,
I need to pass dyanamic datasource to TransactionManager,,
The following article explain how to get Dyanamic Datasource using ibatis
and spring.Similar way i need to pass the dyanamic datasource to
TransactionManager,
http://opensource.atlassian.com/confluence/oss/pages/viewpage.action
My fundamental question was:
Is there a way to achieve optimistic locking using timestamp attribute, if
the "OldObject" and/or the update timestamp of the old object is available
in scope.
All the solutions require you to keep the "OldObject" in scope because, the
where clause; requires you to
That's just going to use the pool defined by the container. Tomcat,
jboss, whatever - that's where you'd need to change things.
Larry
On Thu, Oct 9, 2008 at 2:39 AM, mfs <[EMAIL PROTECTED]> wrote:
>
> Ok, well these would sound funny, but i didn't knew at all before today that
> iBatis DAO frame
Ok, well these would sound funny, but i didn't knew at all before today that
iBatis DAO framework uses connection pooling internally. Anyways i am
somewhat struggling to figure out as to how to disable it..I dont have any
attribute relating to it (and thats why didnt knew at all) but apparently a
12 matches
Mail list logo
