AW: What about JDO project ?

Hi Tom, IMO this is not good news. It does not affect my work at the moment, but my intent was to change my PB implementation to JDO when available with OJB 2.x. I'd rather stay with OJB than restarting with JPOX. Did the OJB team stop the activities concerning JDO? Is it planned to make a

Re: lazy loading 1.0.4

Armin, I looked at it a little better and it is because i have my own cache for model and view objects because they are used so much. I think that I also understand why the initial organisation query only queries the organisation and country table while there are a lot more references. When the

strange ojb behavior with collection

Dear ojb user, i've got a question about the behavior of OJB (1.0.3). If i ask for a collection of vehicule OJB fetch the data from the database to build the collection the expect bellow show what P6SPY catch : [11/01/06 12:13:23:808 CET] 78faf5a0 SystemOut O

Collection problem 1:n relationship

Hello, I've got a simple problem of collection's retrieve : There are 2 tables : InfoData and ValueData with foreign key and datetime field as it's describe in my repository class-descriptor class=InfoData table=INFO_DATA field-descriptor name=id column=ID jdbc-type=INTEGER

Re: bad sql on n-m relation to subclassed object

hi nicolas, i'm pleased the latest version works for you. could you please post the error, or give me a hint where you found discussions about the bug. jakob delahaye.nicolas schrieb: Hi jakob, Ok, it is working with 1.0.4. But if i want retreive the super class alone, a wrong SLQ query

RE: OJB 1.0.4 and ODMG Database.makePersistent

Armin, thanks for your reply. We have transactions that span multiple web requests (pages) and we use the PK values to identify objects that have been persisted on the various pages (in order to re-display the contents of the objects if the user goes back to one of those pages). There are

Re: uses OUTER JOIN by default... -- BUG or FUNCTIONALITY ?

hi sergey, ojb just tries to be clever ;) outer joins are created when there are extents etc. could you please post the relevant parts of your mapping file and the generated sql. jakob Manukyan, Sergey schrieb: After some tests found out that OJB generates LEFT OUTER JOIN instead of

Re: OJB 1.0.4 and ODMG Database.makePersistent

Hi Dirk, Kessler, Dirk wrote: Armin, thanks for your reply. We have transactions that span multiple web requests (pages) and we use the PK values to identify objects that have been persisted on the various pages (in order to re-display the contents of the objects if the user goes back to one

RE: uses OUTER JOIN by default... -- BUG or FUNCTIONALITY ?

Hi Jacob, Well, see yourself if it is a clever behavior: Here is a simplified repository data: class-descriptor class=Supplier table=SUPPLIER field-descriptor name=pkField primarykey=true / field-descriptor name=fkField / collection-descriptor name=allChildren

Configurable interface for LockManagers

I've created my own LockManager implementation for OJB 1.0.4 that implements the Configurable interface and I've added some of the properties this implementation needs to the OJB.properties file. By doing so I was hoping that my LockManager would be configured at some point, like in the