Bobby Lawrence wrote:
Thanx Robert.
I am letting OJB handle the PK/FK stuff - that is the problem is seems.
I have one object, but I want to change a field...this field is a PK.
I want OBJ to update, but it inserts a new one...
--Bobby
I could be wrong as I am not very familiar w/ the internals of OJB's
code, maybe one of the commiters can help more, but my understanding is
that if you change a PK then OJB is going to interpret this as
new/different object than before, since the PK is what it is using to
track identity. You can setup SQL debugging to see the exact statements
generated; but my guess is that the best you are going to be able to do
is: clone your Object, delete the old object, add the new object (using
a custom sequence manager). If you really want to take things into your
own hands I guess you could get a java.sql.Connection object from OJB
and use that to issue SQL update commands, then flush the object cache...
--
Robert r. Sanders
Chief Technologist
iPOV
(334) 821-5412
www.ipov.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
