Hi again, > Not sure I fully understand yet the Identity change. > Sounds like you are saying internal state was inconsistent?
No, don't misunderstand me I only made presumptions - begin a X-file ;-) I'm not very familiar with this part of OJB source (Jakob, Thomas and Matthew are the specialists for that stuff). regards, Armin ----- Original Message ----- From: "Andrew Gilbert" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]>; "Armin Waibel" <[EMAIL PROTECTED]> Sent: Friday, February 28, 2003 9:43 PM Subject: RE: OJB test failures Armin, Thank you very much for this! I will build latest and re-test soon. The bummer is, it would be a major impediment to our use of OJB if we couldn't convert on pk fields. We use a custom GUID impl for the pk in many of our BO's and tables. Not sure I fully understand yet the Identity change. Sounds like you are saying internal state was inconsistent? > ###### > I think the made changes are correct, because the conversion > was not transparent for the user of the Identity object. I suggest > never use converted (java --> sql) pk fields within Identity > (I don't know if code base is comply with this suggest, > maybe that's the reason for the hassle). > The conversion could be done when it's necessary. > But nevertheless I think there is a nasty bug when using > field conversion with pk fields. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
