Actually it's isn't doing a real insert, but is executing a SELECT SQ_anything.NEXTVAL from DUAL and doing a setId() in my object, but the database operation was a UPDATE. In the screen (in my app) appear that the object was inserted, because the Id was incremented. BTW, an Id was wasted due unnecessary .NEXTVAL...
I think it's a bug, doesn't? Of couse, disabling just the "reference" portion of .XML file in main object, all came to expected. Edson Richter ----- Original Message ----- From: Edson Carlos Ericksson Richter To: 'OJB Users List' Sent: Friday, October 31, 2003 3:43 PM Subject: More 1:0..1 optional mapping trouble Hi! Now, if I update an object that hasn't the 1:1 optional mapping, ojb is always inserting a new object!!! Presently there are two serious bugs in 1:1 optional mappings: 1) If using proxies, and the optional side is NULL, it don't return true if comparing (optional==null). 2) If not using proxies, and the optional side is NULL, OJB always does an insert of a new object. I will appreciate any tips, Edson Richter --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.534 / Virus Database: 329 - Release Date: 31/10/2003 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
