Hi Guys, I would like to ask some help regarding the issue below. DataNucleus.Persistence : Error : Could not find API definition for name "JDO". Perhaps you dont have the requisite

The message is very clear. You seemingly don't have the jar `datanucleus-api-jdo.jar` in the CLASSPATH. That jar contains a file `plugin.xml` and if it isn't found then features cannot work.

I am able to utilize extension point="org.datanucleus.store.rdbms.rdbms_mapping" so that all new Boolean columns created will be of type smallint instead of bit. Is there an easy way alter all tables

I don't think there is any handling for that. Using something like Liquibase for schema management maybe would offer that though? never used it so you'd have to find out

I am trying to add support for Oracle NoSQL DB, but I am not getting any good enough documentation. I am trying to follow this link

Hello, "Good" is clearly subjective. Only you know what your experience level is, and so what you are needing. Since it is left to one person to write such documentation, and that one person doesn't

Hello Andy, thanks for your quick response. I appreciate your effort and dedication, I know how difficult it is to do all the things single handed. Sorry for not being clear, what I meant by "good"

Since Java 6 / JDBC 4 it has been possible (and normal practice) to open a Connection without specifying the driver or attempting to load its class. Unfortunately if I omit the driver name in

Any "behaviour" can be changed because the code is open source. People can contribute GitHub Pull Requests

True, but before putting in the effort I prefer to discover if the project maintainers are in favour of such a change. I also don't know if a similar problem afflicts other JPA implementations. I

Since JPA and JDO specs were written for earlier JDKs then I guess they have never been updated to reflect what more recent JDBC specs mandate. Since DataNucleus (v5+) supports JRE 1.8+ ONLY then

See https://issues.apache.org/jira/browse/JDO-771

Is it possible to control the quoting of identifiers. I am using Postgresql (with JPA) and, by default, all tables and column names are created as upper case. This is unnatural for that database

The mechanism you quoted is the way to change case. That is what there is. If that doesn't meet your needs you get the code and contribute some feature

The DataNucleus Forum is planned to be DELETED permanently in February/March 2018. The MVNForum software that it used hasn't been updated for years, and the number of spammers who try to post their

I have created a test case (attached) that reproduces this issue. The class diagram is: The test case also does a dump of the AirCraftController (atc) table schema and its records in the H2 database

I have an application that, upon initial startup, creates about a 100,000 objects in a h2 database (using JDO). Each object is committed in its own transaction. About half way through, the log spits

"EC.preCommit" will only ever be in that 1 class (EC = ExecutionContext(Impl)). And the L1 cache will only ever be updated in that 1 class. Consequently if there is a NULL value in the L1 cache you'd

I think I figured it out. The problem only surfaced when running on Java 9.0.1 inside a Docker container when heap was exhausted (but no OutOfMemory errors displayed). Moving back to Java 8_151

This is fixed in datanucleus-rdbms version 5.1.6.