Hi I try to migrate a legacy application (on Kodo 3.4, develped over 10+ years). I now created all needed plugins so our very much not JDO compliant code runs. However, now that it works I have a mass

Hello, I am migrating from 2.x to 5.x and getting below exception during runtime, please advice how to fix this issue. datanucleus.query.resultSizeMethod of "COUNT" is only valid for use with JDOQL or

According to JDO Mapping Guide ( https://www.datanucleus.org/products/accessplatform_5_1/jdo/mapping.html#_defining_the_current_user ) , to support auditing @CreateUser, we could define an implementat

Hi everyone, I use JDOQL with Datanucleus 4 and Spanner as backend. I use Spanner as a backend for some time and it works mostly fine. But recently I hit a problem when there are too many OR statement

When persisting this model with datanucleus-mongodb @PersistenceCapable public class Room implements Serializable { @PrimaryKey @Persistent(valueStrategy= IdGeneratorStrategy.IDENTITY) private String

What would be the Datanucleus/JDO implementation to this: Suppose I have a POJO, `Hub` which represents a place/location: ```java class Hub { List<Schedule> schedules; } ``` And a `Schedule` class to

Hello, As part of migration from 2.x to 5.x, we are facing a error because the select statement is having ambiguous column name. Same code was working with previous version, looks like we have to chan

Hi, Since I added optimistic locking, with a numeric version attribute, the deletion doesn't work. ERROR DataNucleus.Persistence - Object with id "1" in table I18N_MESSAGE has no version set on the ob

Hello, I am migrating from 2.x to 5.x and all my old code is around javax.jdo.spi.PersistenceCapable(types casting from object type etc). But now when I enhanced my classes using latest version, I can

Hello, I am migrating from Datanucleus version 2.0.4 to 5.x. In 2.0.4 version, length for DB2, CLOB columns used to come as "1M" when schema gets created. Now, in 5.2.3, length for DB2, CLOB columns i

Hello all, I have defined a java class using the default attributes: @PersistenceCapable(detachable = "true") public class PropertyTemplate { ... private String description; ... } And stared using the

I have used https://www.datanucleus.org/products/accessplatform/jdo/query.html#stored_procedures to build code but that did not work.

I have seen rumours of Datanucleus running on Android. I assumed it would because of SQLite support, but this was a mistake. Before I switch to a different persistence method, is there any way that Da

Hi everyone, I am implementing an RDBMS adapter for the GCP Spanner DB. I encounter a problem with transactions and metadata operations. Spanner DB supports information schema queries ( https://cloud.

I am doing version upgrade of Datanucleus jars. Now, during compilation, I am getting below stacktrace in DataNucleus.log. (main) ERROR [DataNucleus.Enhancer] - Error thrown enhancing with ASMClassEnh

After updating of DataNuleus from version 3.3 to 5.2, I get the following error from the query, which limits the max. fetch depth. This Query works correctly with DataNucleus 3.3. java.lang.ArrayIndex

Hi, When I use an attribute converter on an attribute, DN does not load the length validation attribute, keeping its default 255 value. (debug shows the length attribute is 255, probably not loaded) T

Has anyone else seen this issue before? Everything has been working fine for all MySQL 5.x versions but after exporting the database as a SQL dump from 5.7 and importing the SQL dump into a new MySQL

We've just migrated to version 5 and occasionally get the following warning: Query - >> Currently do not support adding restriction on discriminator for table=mytableA f0 to class MyClassB where: myta

After my misguided attempt to get some help on github I'm trying to do it correctly here (: I'm in the midst of setting up a JavaFX project with Datanucleu + JDO + JDOQL. I've got the first two parts