forgot one thing:
when you store an Acknowledgement without a Project the projectID will be set to null, because no Project is associated. this happen regardless of auto-update in the reference-descriptor. if projectID is a primitive null is ignored (which is a bug imho leading to other problems :( )
hth jakob
[EMAIL PROTECTED] wrote:
This is exactly the question I had posted below on "subobjects." I think I am missing an understanding, but when I populated the subobject first, it placed the id into the database. Otherwise I got within tracing:
[org.apache.ojb.broker.core.PersistenceBrokerImpl] INFO: Cascade store for this reference (RegionVO) was set to false.
JohnE
----- Original Message ----- From: Jason McKerr <[EMAIL PROTECTED]> Date: Wednesday, June 25, 2003 12:20 pm Subject: Foreign Key column not getting updated
Hey guys,
I'm having a problem with a nullable foreign-key column not getting updated.
I've got a table (Acknowledgements) that has a foreign key to the
Project table.
Now if I have all of the columns set for acknowledgements (including
projectID) all of the columns except projectID are getting set when I
call store(). The projectID is getting set to null.
If I comment out the reference call to Project from the Acknowledgementtable in my repository, the column gets set normally.
So the question is: Can I not just do an insert without a complete
object reference? I'm doing a lot of this over serialized XML so it's
not cool to have to pass an object graph just to do an isnert on a minorrelated table.
Jason
------------------------------------------------------------------- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
