Hi,
in the JDO2-final spec 13.4.5
Once a transaction has been marked for rollback via setRollbackOnly, the
commit method will always fail with JDOFatalDataStoreException. The JDO
implementation must not try to make any changes to the database during commit
when the transaction has been marked
Hi Andy,
Good catch. It's definitely a spec bug that I expect that we should
fix in a maintenance release.
Please file a JIRA. We should probably have a test case written for
it as well.
Thanks,
Craig
On Nov 13, 2006, at 4:52 AM, Andy Jefferson wrote:
Hi,
in the JDO2-final spec 13.4.
Hi,
Working in real-world applications using JDO 2.0 I beware about the SQL IN
equivalend operator missed by spec. An example:
public class Questionnaire{
...
private Employee employee;
...
}
I'd like to get any Questionnaire instances for the following employee:
Luca, Robert and Chris. The
Hi Luca,
the JDOQL query you specified below should work as it is today. As you
said the contains operator expects a collection on the left. This
collection may be a collection parameter and does not need to be a
collection field.
Regards Michael
Hi,
Working in real-world applications usin
Hi,
Working in real-world applications using JDO 2.0 I beware about the SQL IN
equivalend operator missed by spec. An example:
public class Questionnaire{
...
private Employee employee;
...
}
I'd like to get any Questionnaire instances for the following employee:
Luca, Robert and Chris. The
Hi Luca,
The specification does support the usage you mention. See below...
On Nov 13, 2006, at 7:29 AM, Luca Garulli wrote:
Hi,
Working in real-world applications using JDO 2.0 I beware about the
SQL IN
equivalend operator missed by spec. An example:
public class Questionnaire{
...
pr
Why not? Have you tried with JPOX ?
Quoting Luca Garulli <[EMAIL PROTECTED]>:
> Hi,
> Working in real-world applications using JDO 2.0 I beware about the SQL IN
> equivalend operator missed by spec. An example:
>
> public class Questionnaire{
> ...
> private Employee employee;
> ...
> }
>
>
Hi Luca,
Craig is right, I overlooked you tried to declare list as a variable. So
the query works if you declare list as a parameter, so calling
query.declareParameters("java.util.Collection list" ) instead of
query.declareVariables.
Regards Michael
Hi Luca,
the JDOQL query you specified b
Hi,
Tested with JPOX and effectly works!
I'd had a look round in my memory, in the JPOX, Solarmetric documentation
and a fast look also in JDO spec, but I didn't find any use case like mine.
Thanks,
Bye Luca
-Messaggio originale-
Da: Erik Bengtson [mailto:[EMAIL PROTECTED]
Inviato: lune
Transaction.setRollbackOnly() : difference between api20 and spec
-
Key: JDO-442
URL: http://issues.apache.org/jira/browse/JDO-442
Project: JDO
Issue Type: Bug
Compone
Change column name in InstanceCallbacks table
-
Key: JDO-443
URL: http://issues.apache.org/jira/browse/JDO-443
Project: JDO
Issue Type: Improvement
Components: tck2, tck2-legacy
Affec
11 matches
Mail list logo