Thank you Andy for pointing me to the right point in the documentation.The problem arose because I forgot setting the persistence property "datanucleus.query.sql.allowAll" to true. This caused my

JDO (and JPA) don't do automatic changes to schema. They do CREATE or DELETE only. Metadata (for schema) is only ever used on a CREATE, and since you already have tables it is up to you to have the

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

You mean, you have a field MYFIELD (with col name MYCOL) of some type that is mapped to BLOB? and if you don't bother specifying the length of the field in metadata then it picks MYCOL

Hello, Thank you Andy for your response. It creates your schema with that in a column - yes I checked the code changes provided by you and it looks like it was removed so that it takes the

Hello, what was in some version from 2010 I've little interest in. You can trace code changes in SourceForge (ancient code) and GitHub (recent code). Likely it is this change. Perhaps you can provide

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

That works for our tests for a database/driver that supports JDBC CallableStatement API, as per this link. These tests are public, and anybody can contribute to them, just like they can the code (not

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

Looks like you added the missing javax.* classes, as per this.

...and here's another repo that might be interesting: https://github.com/cloudstore/cloudstore-android The last commit-comments state "cloudstore droid working with DN" and "PersistenceManager can be

It's quite a while, but I definitely got DataNucleus running on Android. I wrote a test-program and it worked fine. You already found my pull-request, which fixed quite a few issues in the

Only you can decide what is "right" for your database, but requiring a CONNECTION "read only" (presumably this database has a JDBC driver and require a call of Connection.setReadOnly?) and changing

Thanks for the response. I noted that only 5.2 is open for merge. After your comment, I've dug deep and I've seen that it is possible to request a new connection for value-generation with a different

Hi, Firstly the only source that is supported is current (5.2) so that's the only chance anything would have of being merged, FYI. Secondly, do you have some particular stack traces that show where

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 with read-only

Thanks Andy. Your point is correct. After changing source, target properties to 1.6(changing which was also trouble as it is a big project and resulted in other errors) classes were enhanced fine. I

In the absence of any further info, the classes being enhanced are likely the problem then. ASM is clearly getting upset about some bytecode, and if it works when compiling classes using JDK1.8 then

My bad that I mentioned about ASM v5.0.3, even in stack trace it is org.datanucleus.enhancer.DataNucleusEnhancer. I saw that reference and mentioned ASM v5.0.3 by mistake.

Only you know what the differences are between the situations you refer to. In StackOverflow you say you are using ASM v5.0.3 (not mentioned here at all). If you are using DataNucleus v5.2 then you