|
Re: datanucleus.query.resultSizeMethod of "COUNT" is only valid for use with JDOQL or JPQL currently
Since you are the only person who sees this, I suggest you get the code and work it out
Since you are the only person who sees this, I suggest you get the code and work it out
|
By
Andy
·
#248
·
|
|
Re: datanucleus.query.resultSizeMethod of "COUNT" is only valid for use with JDOQL or JPQL currently
Hello Andy,
In the same issue, we minimized the extensions and ran the query with below two extensions but our sample program is going into infinite loop in execute method. Please find attached the
Hello Andy,
In the same issue, we minimized the extensions and ran the query with below two extensions but our sample program is going into infinite loop in execute method. Please find attached the
|
By
mayank.chawla@...
·
#247
·
Edited
|
|
Re: datanucleus.query.resultSizeMethod of "COUNT" is only valid for use with JDOQL or JPQL currently
That is not a "testcase". A "testcase" is something that, when run, returns SUCCESS, FAILURE or ERROR dependent on how it performs and how it is coded based on expectations.
That aside, you decide to
That is not a "testcase". A "testcase" is something that, when run, returns SUCCESS, FAILURE or ERROR dependent on how it performs and how it is coded based on expectations.
That aside, you decide to
|
By
Andy
·
#246
·
|
|
Re: datanucleus.query.resultSizeMethod of "COUNT" is only valid for use with JDOQL or JPQL currently
Problem Description and Reproduction
We were able to reproduce the problem in a small standalone program. We took the samples available from
https://github.com/datanucleus/samples-jdo
We picked the
Problem Description and Reproduction
We were able to reproduce the problem in a small standalone program. We took the samples available from
https://github.com/datanucleus/samples-jdo
We picked the
|
By
mukul.gupta@...
·
#245
·
|
|
Re: datanucleus.query.resultSizeMethod of "COUNT" is only valid for use with JDOQL or JPQL currently
https://www.datanucleus.org/documentation/problem_reporting.html
https://www.datanucleus.org/documentation/problem_reporting.html
|
By
Andy
·
#244
·
|
|
Re: datanucleus.query.resultSizeMethod of "COUNT" is only valid for use with JDOQL or JPQL currently
Hello,
Query results are accessible, once the result is returned, we cast it into Iterable. When we call hasNext() on Iterable method, flow goes into Datanucleus layer as hasNext() method is overriden
Hello,
Query results are accessible, once the result is returned, we cast it into Iterable. When we call hasNext() on Iterable method, flow goes into Datanucleus layer as hasNext() method is overriden
|
By
mayank.chawla@...
·
#243
·
|
|
Re: How to use datanucleus.CurrentUserProvider?
The "persistence properties" are amply defined in the docs. "datanucleus.CurrentUserProvider" is one of them.
As said, you are using
PersistenceManagerFactory pmf = new
The "persistence properties" are amply defined in the docs. "datanucleus.CurrentUserProvider" is one of them.
As said, you are using
PersistenceManagerFactory pmf = new
|
By
Andy
·
#242
·
|
|
Re: How to use datanucleus.CurrentUserProvider?
I got your point on PersistenceUnitMetaData.
May I ask what is the "persistence properties" if it doesn't mean JDOPersistenceManagerFactory.setPersistenceProperties()? I am new to datanucleus, your
I got your point on PersistenceUnitMetaData.
May I ask what is the "persistence properties" if it doesn't mean JDOPersistenceManagerFactory.setPersistenceProperties()? I am new to datanucleus, your
|
By
1919wang@...
·
#240
·
|
|
Re: How to use datanucleus.CurrentUserProvider?
I didnt mention JDOPersistenceManagerFactory.setPersistenceProperties(), no.
PersistenceUnitMetaData is to replicate the file "persistence.xml" content. You cannot specify an Object in a text-based
I didnt mention JDOPersistenceManagerFactory.setPersistenceProperties(), no.
PersistenceUnitMetaData is to replicate the file "persistence.xml" content. You cannot specify an Object in a text-based
|
By
Andy
·
#239
·
|
|
Re: How to use datanucleus.CurrentUserProvider?
Thanks Andy.
I have several more questions:
The 1st option you mentioned is `JDOPersistenceManagerFactory.setPersistenceProperties()`, right? The underlying logic of those 2 options seems identical
Thanks Andy.
I have several more questions:
The 1st option you mentioned is `JDOPersistenceManagerFactory.setPersistenceProperties()`, right? The underlying logic of those 2 options seems identical
|
By
1919wang@...
·
#238
·
Edited
|
|
Re: How to use datanucleus.CurrentUserProvider?
You create an INSTANCE of your CurrentUserProvider, and specify that as the value of "datanucleus.CurrentUserProvider" to the persistence properties.
If you insist on creating a PMF in that way you
You create an INSTANCE of your CurrentUserProvider, and specify that as the value of "datanucleus.CurrentUserProvider" to the persistence properties.
If you insist on creating a PMF in that way you
|
By
Andy
·
#237
·
Edited
|
|
How to use datanucleus.CurrentUserProvider?
According to JDO Mapping Guide, to support auditing @CreateUser, we could define an implementation of the DataNucleus interface CurrentUserProvider, and specify it on PMF creation using the property
According to JDO Mapping Guide, to support auditing @CreateUser, we could define an implementation of the DataNucleus interface CurrentUserProvider, and specify it on PMF creation using the property
|
By
1919wang@...
·
#236
·
|
|
Re: datanucleus.query.resultSizeMethod of "COUNT" is only valid for use with JDOQL or JPQL currently
I have zero problem accessing a query result after transaction commit, with scrollable results. You still haven't posted anything resembling a stack trace with current versions, nor a way of
I have zero problem accessing a query result after transaction commit, with scrollable results. You still haven't posted anything resembling a stack trace with current versions, nor a way of
|
By
Andy
·
#235
·
Edited
|
|
Re: datanucleus.query.resultSizeMethod of "COUNT" is only valid for use with JDOQL or JPQL currently
Hello,
After further debugging we found - our application goes into Datanucleus layer twice in this flow. First time it creates query, execute it and return result. While returning the result,
Hello,
After further debugging we found - our application goes into Datanucleus layer twice in this flow. First time it creates query, execute it and return result. While returning the result,
|
By
mayank.chawla@...
·
#234
·
|
|
Re: DyadicExpression "OR" compiles into nested SQL expressions which exhausts the stack of the underlying DB
Thanks Andy, "contains" has worked. It uses the "IN" statement.
I have been confused about the behavior of the "OR" statements. I have expected something like (x OR y OR z) instead it is (((X) OR Y)
Thanks Andy, "contains" has worked. It uses the "IN" statement.
I have been confused about the behavior of the "OR" statements. I have expected something like (x OR y OR z) instead it is (((X) OR Y)
|
By
yunus@...
·
#233
·
|
|
Re: DyadicExpression "OR" compiles into nested SQL expressions which exhausts the stack of the underlying DB
What SQL do you want to generate??
The JDOQL you provided has been mapped directly as you requested it.
You could try having a single parameter of type Collection that has multiple String values, and
What SQL do you want to generate??
The JDOQL you provided has been mapped directly as you requested it.
You could try having a single parameter of type Collection that has multiple String values, and
|
By
Andy
·
#232
·
Edited
|
|
DyadicExpression "OR" compiles into nested SQL expressions which exhausts the stack of the underlying DB
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
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
|
By
yunus@...
·
#231
·
|
|
Re: datanucleus.query.resultSizeMethod of "COUNT" is only valid for use with JDOQL or JPQL currently
Only you can see it, hence only you can debug it. Check you're not multithreading things. Reproduce it in a testcase. That's all there is.
Only you can see it, hence only you can debug it. Check you're not multithreading things. Reproduce it in a testcase. That's all there is.
|
By
Andy
·
#230
·
|
|
Re: datanucleus.query.resultSizeMethod of "COUNT" is only valid for use with JDOQL or JPQL currently
Hello,
After debugging the code I found it is going in the below flow, I ran the queries that were formed, copied them through logs and ran them at DB2, all queries executed correctly but returned no
Hello,
After debugging the code I found it is going in the below flow, I ran the queries that were formed, copied them through logs and ran them at DB2, all queries executed correctly but returned no
|
By
mayank.chawla@...
·
#229
·
Edited
|
|
Re: Converter not working with datanucleus-mongodb
Use of JDO converters to convert a String to a Long is not supported, and is minority interest. Get the code if you require such things
Use of JDO converters to convert a String to a Long is not supported, and is minority interest. Get the code if you require such things
|
By
Andy
·
#228
·
|