RE : RE : BIGINT to Long, FieldConversion ?

Thanks Ricardo ! I would like to know wich kind of link you do : Object A have a reference to B, called bB. If I want to insert in db A, Have to do : A.setbB(instanceB); Or A.setb_FK(id_B_PK); Should I set the bB instance or the FK_Id ? Because I seems that with small long I can do only

RE : RE : Qury on an object Locked but not in Db

Thanks a lot Charles. That 's great ! -Message d'origine- De : Charles Anthony [mailto:[EMAIL PROTECTED] Envoyé : jeudi 7 août 2003 16:07 À : 'OJB Users List' Objet : RE: RE : Qury on an object Locked but not in Db Hi, No, not true. flush will push all the INSERTS and UPDATES

RE: RE : BIGINT to Long, FieldConversion ?

I use BIGINT for my primary keys and Long for class fields and everything goes ok. Ricardo. -Original Message- From: Emmanuel Dupont [mailto:[EMAIL PROTECTED] Sent: viernes, 08 de agosto de 2003 18:29 To: 'OJB Users List' Subject: RE : BIGINT to Long, FieldConversion ? More

RE : BIGINT to Long, FieldConversion ?

More information : it faills on the FK key (not null column), null is put in the assignReferenceFKs method from PersistenceBrokerImpl... -Message d'origine- De : Emmanuel Dupont [mailto:[EMAIL PROTECTED] Envoyé : vendredi 8 août 2003 17:35 À : OJB Users List Objet : BIGINT to Long,

Re: Compile for JDK 1.3?

Hi Daniel, It's a slip with the RC4 releas. we normally provide build compatibility for jdk 1.2, 1.3 and 1.4. You can either use JDK 1.4 or remove the source package o.a.ojb.otm to work around this issue. Will be fixed with next public release. cheers, Thomas [EMAIL PROTECTED] wrote: I am

Re: Re: Prefetched Relationship for M:N collection

ÔÚ 2003-08-09 10:56:00 ÄúдµÀ£º Thanks for Your answer.of you ? Could you tell me ? Thanks~~ here uou are stack trace: java.lang.ArrayIndexOutOfBoundsException: 0 at org.apache.ojb.broker.accesslayer.CollectionPrefetcher.buildPrefetchCriteriaMultipleKeys(CollectionPrefetcher.java:184)

Updates treated as inserts by ODMG

Hello, I have a VO defined as follows: class ResultSetVO { Object id String label; int maxRows; // details ommitted }; --- class-descriptor

RE: one table - multiple classes problem

Hi, you can do it without problem. I have two classes for one table. Classes: Crm_cliente_masinfo, Crm_cliente_general Table: CRM_CLIENTE (1)First xml descriptor. !-- This repository file is generated by the impart OJB Generator -- !-- www.impart.ch [EMAIL PROTECTED]

Re: PROBLEM: same table name in different databases

Julisys -- I had the same problem myself. The solution is to simply set the schema attribute on the two class-descriptors. This will cause ojb to treat those class-descriptors separately. Ron Gallagher Atlanta, GA [EMAIL PROTECTED] From: JUliSys [EMAIL PROTECTED] Date: 2003/08/08 Fri AM

Re: Is it OK to use JDO now.

Hi: Short answer: Yes, you can use it. Long answer: I think the statement below must be rewrote, because I had the same question as you some days ago. :) OJB already work with JDO. You can use it. Currently, the OJB support for JDO is full working. OJB currenlty use the Sun JDO implementation.

Re: Updated repost: Questions about ODMG testcase PersonWithArrayTest.testStoreThreePersons

Hi Tom, I update the test case to show your problem. regards, Armin - Original Message - From: Thomas Dudziak [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 12:14 PM Subject: Updated repost: Questions about ODMG testcase