http://db.apache.org/ojb/faq.html#What%20are%20the%20differences%20between%20the%20PersistenceBroker%20API%20and%20the%20ODMG%20API?%20Which%20one%20should%20I%20use%20in%20my%20applications?
Corey wrote:
Hi all,
Sorry, newbie posting here. I've read all the docs and played with all of the tutorials, but now I need some advice. The question is whether to code directly to the PB or to code to ODMG or JDO. I'm attracted to the simplicity of the PB but am concerned about the management of 1:n or m:n relationships between objects. The documentation indicates that when using the PB, the relationships between collections of objects would need to resolved manually using the link() and unlink() calls. The document also seems to indicate that this would not be the case if ODMG were employed. Can anyone iterate over the good, bad and ugly of one method verses the other? Looking for the voice of experience here.
Thanks --Corey ______________________________________________________ William C. Brown Chief Architect. Spectrum Software Inc.
11445 Johns Creek Pkwy Duluth, GA. 30097. Suite 300. Tel > 770.813.4952 e > [EMAIL PROTECTED] web > www.spectrumscm.com yahoo > caldron68
----- Original Message ----- From: "Rajani" <[EMAIL PROTECTED]>
To: "OJB Users List" <[EMAIL PROTECTED]>
Sent: Monday, May 24, 2004 7:30 AM
Subject: Problem reading a clob object
Hi All,
I'm using oracle 8i database. The table has a column with the data-type as CLOB which we are using to store xml data. It is mapped to String data type in the java object. I have no problem inserting xml data with this mapping. But when i try to fetch the record using persistence broker, Its failing to retrieve the data. Can anybody throw some light on this problem?
Thanks Rajani
--------------------------------------------------------------------- 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]