RE: [FAQ] Re: Why select by insert?

Thomas, Is there any equivalent features in ODMG api? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 08 August 2003 14:15 To: OJB Users List Subject: [FAQ] Re: Why select by insert? Hi, pb.store(obj) must check if obj is already stored in the db or not to

Re:References Talking Smack

Hi Laugusto, Thanks for letting me know I'm not alone :) Just curious... I reported two problems... 1) When using numeric wrapper classes OJB tries to insert nulls in fk's if I don't do a retrieveAllReferences() first. 2) When I try to do a retrieveAllReferences() first, it complains that the

RE: JDO - Objects fetched from DB are in transient state, not persistent

Hi Ketan, Thomas, I was wondering if you'd been able to determine the right way to proceed with this. I hope to fix the problem within the next 3 weeks. If I understood correctly before, the JDO layer is broken and has been for some time. But that can't be right, since other

Looks like we are on the right way :)

Hi OJBers: I read this survey and want to share it with the community: http://sdtimes.com/news/083/story5.htm Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:

Re: one table - multiple classes problem

hi, ojb fires a query for each extent (subclass) residing in it's own table. extents in the same table (using ojbConcreteClass) are retrieved with one query. this behaviour has the advantage that it runs on all dbms (an alternative would be to use UNION) ! on the other hand, we need

RE: RE : RE : BIGINT to Long, FieldConversion ?

You have to put the B instance. If there is a relation between the two classes in repository.xml you must use object instances. Otherwise you must use the class A field id attribute. Ricardo. -Original Message- From: Emmanuel Dupont [mailto:[EMAIL PROTECTED] Sent: viernes, 08 de

Re: JDO - Objects fetched from DB are in transient state, not persistent

Thomas, I tried your suggestion. I don't know how to interpret the results, though :-). I changed the code fragment to: PersistenceManagerFactory pmf = new OjbStorePMF(); PersistenceManager pm = pmf.getPersistenceManager();

Compile for JDK 1.3?

I am following the quickstart.html directions and trying to run bin\build junit using JDK 1.3.1. It looks like a targeted effort was made to get this work with JDKs other than 1.4. However, the compile fails due to a dependency on a JDK 1.4 class. Is this a bug? or must we use JDK 1.4 or

Re: Why not insert null?

Hi, I see only two reasons why OJB would write values into a timestamp column: 1. you have set the attribute locking=true in the field-descriptor 2. you are using a ConversionStrategy that modifies the column. cheers, Thomas lyl wrote: Thanks for ketan's response, but I don't think it is caused

M:N question

Hello, I have a emergent question.Here I have designed 3 tables:User Domain Role and I have implemented User - Role M:N relation by add a table User_Role including the PK of table User Role and write repository xml file(collection-descriptor, fk-pointing-to-this-class