Thanks; will look into that more closely. Can you give me a pointer where to find the fieldindex -> fieldname mapping? I was am unable to identify for a certainty which index is which field. I'm

opensource development on such complex product (closely comparable to database software development) requires a big big expertise on the product design, constraints, ... which I don't have (yet) on

JDO/JPA API calls are processed in the appropriate order. If a required statement is batchable then it is batched. Referential integrity is always assumed.

I mean when performing modifications, do something like: -1 set constraints deffered => disable foreign-key, unique constraints, ... -2 Batch updates table per table (addBatch, ...) - perform

You mean DELETE them in the datastore, do random operations, then re-CREATE them? Or do a datastore-specific disable (such as MySQL set foreign_key_checks=0). Nope. But then its open source so anyone

That metadata extension works for me in this sample. How you apply it is up to you

Hi, Are there any options to deactivate foreign-key constraints, then insert/update/delete table per table using batches, and then reactivate foreign-key at the commit ? I used a product with that

An L1 cache is an object cache, as defined by the JDO spec. You have an "id" you get the equivalent persistable object. It is used anywhere a persistable object is accessible, and that includes

I've tried to add the extension definition to my package jdo file but either it isn't working as I expect, or I've defined it incorrectly. This is what I added: <field name="addPerson"

I've been encountering something I don't understand with the Query caches and the L1 cache. I've tried reading the DN docs a few times, but I am still confused by the results I am seeing. My

With a single object relation with the FK at the selected object side there are only 3 things that would be feasible. Load the related object, instantiating it. Put it in the fetch plan for

Thanks Andy. Fair enough (embedded vs related). I forgot to mention the fetch-groups. Indeed, I have no fetch groups explicity defined - either in the mapping file nor in the API usage. Everything

Audit fields "addPerson" and "modPerson" aren't embedded (exist in the same table), they are related (have their own table), using JDO terminology ... or at least without seeing your mapping

I'm having some strange RDBMS N+1 calls most likely due to my mappings, but am not sure if this is a DN Persistence configuration issue or a mapping issue. I'm using MSSQL. My problem is that I have

Thanks for the tip. I was looking for a `clearCache` or a `clearMetadata` method or something to that extent that I didn't notice the `unmanage/unload` methods. I also found the plugin from Dan

There is a MetaDataManager for each PMF. It loads metadata when it needs to. There is a method unloadMetaDataForClass to unload a class' metadata if needing to do so. There is also a method on

I'm working on a fairly large, slow startup legacy application in which I am slowly trying to integrate DataNucleus. I am also leveraging JRebel, which allows me to modify most classes on the fly

Hi, I'm running into a similar problem as you where I need to create an ugly JDOHelper.getObjectIdAsLong() hack as well due to some legacy Kodo code. Did you get something fully functional finally?

Hi, When 2 queries with the same tenant but different tenantReaders are executed, the second one returns the result of the first one. The SQL generated is the same for the second query while it should

You are using a JEE connection pool but are setting the resource type as "local" hence DN will try to commit the connection (since it commits local things). Your connection (JBoss JCA) then throws an