You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by Michelle Caisse <mc...@sonic.net> on 2010/12/03 05:09:22 UTC
JDO TCK Conference Call Friday, Dec 3, 9 am Pacific Time
Hi,
We will have our regular meeting Friday, December 3, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
-- Michelle
Re: JDO TCK Conference Call Friday, Dec 17, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
PLEASE NOTE: JDO will be on winter break for the next two weeks. Next
meeting: January 7, 2011
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647.
Mostly done but not completely working. Need to update the version
numbers in the pom to be identical to those used in maven 1. Some
tests cannot find the test data resource. The test data reader is
calling the constructor for the spring xmlbeans reader which cannot
find the file. Class path issue?
2. Avg return type - patch available for review https://issues.apache.org/jira/browse/JDO-643
This proposes that integral types and floating point types all return
double for average. Is there a good reason for JDO to be different
from JPA? AI Craig: update JIRA with comment
3. Extend PersistenceManageFactory to return all known entity classes -
new comments https://issues.apache.org/jira/browse/JDO-667
4. Other issues
Take a look at http://www.datanucleus.org/servlet/forum/viewthread_thread,6467
for an interesting idea.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Dec 17, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
PLEASE NOTE: JDO will be on winter break for the next two weeks. Next
meeting: January 7, 2011
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647.
Mostly done but not completely working. Need to update the version
numbers in the pom to be identical to those used in maven 1. Some
tests cannot find the test data resource. The test data reader is
calling the constructor for the spring xmlbeans reader which cannot
find the file. Class path issue?
2. Avg return type - patch available for review https://issues.apache.org/jira/browse/JDO-643
This proposes that integral types and floating point types all return
double for average. Is there a good reason for JDO to be different
from JPA? AI Craig: update JIRA with comment
3. Extend PersistenceManageFactory to return all known entity classes -
new comments https://issues.apache.org/jira/browse/JDO-667
4. Other issues
Take a look at http://www.datanucleus.org/servlet/forum/viewthread_thread,6467
for an interesting idea.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: Query test failure with newer derby version (was Re: Minutes:
JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time)
Posted by Michael Bouschen <mb...@spree.de>.
Hi,
this is the JDOQL query:
SELECT FROM org.apache.jdo.tck.pc.mylib.PCPoint EXCLUDE SUBCLASSES
WHERE (x == 2) == true
and here is the generated SQL:
SELECT 'org.apache.jdo.tck.pc.mylib.PCPoint' AS
NUCLEUS_TYPE,A0.ID,A0.X,A0.Y
FROM APPLICATIONIDENTITY0.PCPOINT A0
WHERE A0.X = 2 = 1
So the question is: what does SQL define when comparing an integer and a
boolean?
The expression "A0.X = 2" evaluates to a boolean which is then compared
to the integer 1.
Regards Michael
> Hi Craig,
>
> [...]
>>>
>>> (2) query test:
>>>
>>> The failing test is in jdoql.conf: class
>>> org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence
>>> method runTestParenthesesMarkOperatorPrecedence08.
>>> The test runs a JDOQL query with PCPoint as candidate class and "(x
>>> == 2) == true" as filter. It results in an exception thrown by the
>>> derby SQL compiler:
>>>
>>> java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER'
>>> are not supported. Types must be comparable. String types must also
>>> have matching collation. If collation does not match, a possible
>>> solution is to cast operands to force them to the default collation
>>> (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename AS
>>> VARCHAR(128)) = 'T1')
>>>
>>> The derby versions 10.6.1.0 and 10.7.1.1 run into this exception.
>>> But it does NOT happen with derby version 10.4.2.0, which we are
>>> using in the maven1 environment.
>>
>> Good catch. Would you have time to file a JIRA with Derby?
>
> First I want to take a look at the generated SQL before filing a JIRA.
> I'll keep you posted.
>
> Regards Michael
>
> [...]
>
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@spree GmbH, Berlin
Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
Amtsgericht Berlin-Charlottenburg HRB 86780 B
USt.-Id. Nr.: DE 225 964 680
Query test failure with newer derby version (was Re: Minutes: JDO
TCK Conference Call Friday, Jan 7, 9 am Pacific Time)
Posted by Michael Bouschen <mb...@spree.de>.
Hi Craig,
[...]
>>
>> (2) query test:
>>
>> The failing test is in jdoql.conf: class
>> org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence
>> method runTestParenthesesMarkOperatorPrecedence08.
>> The test runs a JDOQL query with PCPoint as candidate class and "(x
>> == 2) == true" as filter. It results in an exception thrown by the
>> derby SQL compiler:
>>
>> java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER'
>> are not supported. Types must be comparable. String types must also
>> have matching collation. If collation does not match, a possible
>> solution is to cast operands to force them to the default collation
>> (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename AS
>> VARCHAR(128)) = 'T1')
>>
>> The derby versions 10.6.1.0 and 10.7.1.1 run into this exception. But
>> it does NOT happen with derby version 10.4.2.0, which we are using in
>> the maven1 environment.
>
> Good catch. Would you have time to file a JIRA with Derby?
First I want to take a look at the generated SQL before filing a JIRA.
I'll keep you posted.
Regards Michael
[...]
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@spree GmbH, Berlin
Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
Amtsgericht Berlin-Charlottenburg HRB 86780 B
USt.-Id. Nr.: DE 225 964 680
Re: Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Hi Michael,
On Jan 8, 2011, at 2:33 AM, Michael Bouschen wrote:
> Hi,
>> Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
>>
>> Agenda:
>>
>> 1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
>>
>> Only two tests are now failing: signature test and a query test.
>> The signature test might be reading the wrong signature file, since
>> there have been a few changes to the signature since 3.0.
>
> I looked at the test failures:
>
> (1) signature test:
>
> The current pom.xml still refers the 3.0 version of jdo-api. The
> test succeeds after switching the dependency to 3.1-SNAPSHOT.
>
> Please note the dependency needs to be changed in exectck and tck!
>
> (2) query test:
>
> The failing test is in jdoql.conf: class
> org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence
> method runTestParenthesesMarkOperatorPrecedence08.
> The test runs a JDOQL query with PCPoint as candidate class and "(x
> == 2) == true" as filter. It results in an exception thrown by the
> derby SQL compiler:
>
> java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER'
> are not supported. Types must be comparable. String types must also
> have matching collation. If collation does not match, a possible
> solution is to cast operands to force them to the default collation
> (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename AS
> VARCHAR(128)) = 'T1')
>
> The derby versions 10.6.1.0 and 10.7.1.1 run into this exception.
> But it does NOT happen with derby version 10.4.2.0, which we are
> using in the maven1 environment.
Good catch. Would you have time to file a JIRA with Derby?
Thanks,
Craig
>
> Regards Michael
>>
>> Maven now has a process for publishing Apache artifacts. We should
>> look into what is needed to use the staging and publishing
>> repositories.
>>
>> 2. Other issues
>>
>> https://issues.apache.org/jira/browse/JDO-643 should add the tck as
>> an affected component. We should also add test cases for average of
>> more of the types that we support, including BigDecimal and
>> BigInteger.
>>
>> https://issues.apache.org/jira/browse/JDO-671 The Oracle.com JDO
>> page needs an update.
>>
>> Action Items from weeks past:
>>
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>>
>
>
> --
> *Michael Bouschen*
> *Prokurist*
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon: +49 30 235 520-33
> Fax: +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url: www.akquinet.de <http://www.akquinet.de>
>
> akquinet tech@spree GmbH, Berlin
> Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
> Amtsgericht Berlin-Charlottenburg HRB 86780 B
> USt.-Id. Nr.: DE 225 964 680
>
> --
> *Michael Bouschen*
> *Prokurist*
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon: +49 30 235 520-33
> Fax: +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url: www.akquinet.de <http://www.akquinet.de>
>
> akquinet tech@spree GmbH, Berlin
> Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
> Amtsgericht Berlin-Charlottenburg HRB 86780 B
> USt.-Id. Nr.: DE 225 964 680
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific
Time
Posted by Michael Bouschen <mb...@spree.de>.
Hi,
> Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
>
> Agenda:
>
> 1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
>
> Only two tests are now failing: signature test and a query test. The
> signature test might be reading the wrong signature file, since there
> have been a few changes to the signature since 3.0.
I looked at the test failures:
(1) signature test:
The current pom.xml still refers the 3.0 version of jdo-api. The test
succeeds after switching the dependency to 3.1-SNAPSHOT.
Please note the dependency needs to be changed in exectck and tck!
(2) query test:
The failing test is in jdoql.conf: class
org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence method
runTestParenthesesMarkOperatorPrecedence08.
The test runs a JDOQL query with PCPoint as candidate class and "(x ==
2) == true" as filter. It results in an exception thrown by the derby
SQL compiler:
java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER' are
not supported. Types must be comparable. String types must also have
matching collation. If collation does not match, a possible solution is
to cast operands to force them to the default collation (e.g. SELECT
tablename FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) = 'T1')
The derby versions 10.6.1.0 and 10.7.1.1 run into this exception. But it
does NOT happen with derby version 10.4.2.0, which we are using in the
maven1 environment.
Regards Michael
>
> Maven now has a process for publishing Apache artifacts. We should
> look into what is needed to use the staging and publishing repositories.
>
> 2. Other issues
>
> https://issues.apache.org/jira/browse/JDO-643 should add the tck as an
> affected component. We should also add test cases for average of more
> of the types that we support, including BigDecimal and BigInteger.
>
> https://issues.apache.org/jira/browse/JDO-671 The Oracle.com JDO page
> needs an update.
>
> Action Items from weeks past:
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
>
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@spree GmbH, Berlin
Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
Amtsgericht Berlin-Charlottenburg HRB 86780 B
USt.-Id. Nr.: DE 225 964 680
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@spree GmbH, Berlin
Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
Amtsgericht Berlin-Charlottenburg HRB 86780 B
USt.-Id. Nr.: DE 225 964 680
Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
Only two tests are now failing: signature test and a query test. The
signature test might be reading the wrong signature file, since there
have been a few changes to the signature since 3.0.
Maven now has a process for publishing Apache artifacts. We should
look into what is needed to use the staging and publishing repositories.
2. Other issues
https://issues.apache.org/jira/browse/JDO-643 should add the tck as an
affected component. We should also add test cases for average of more
of the types that we support, including BigDecimal and BigInteger.
https://issues.apache.org/jira/browse/JDO-671 The Oracle.com JDO page
needs an update.
Action Items from weeks past:
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Jan 14, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647.
Changes for parameterizing the version numbers are now checked in. Two
issues remain:
Exception from new Derby version: is the generated SQL correct?
Perhaps not. "Comparisons between 'BOOLEAN' and 'INTEGER' are not
supported." AI Michael: file a JIRA to resolve whether this is a
DataNucleus or Derby issue.
Upgrade to later DataNucleus version: using 2.1.1 now; need 2.2.2-
SNAPSHOT for "average" change. AI Michelle: change the dependency for
the project.
Next: see how to run the tck using an IUT (using profiles).
Also: how can we use the Apache maven release staging repository for
releases? The idea is that the jdo-api could be defined as a maven
dependency and automatically downloaded from the central repository
but the jdo-tck needed to be installed as source. With the tck now
defined as a maven2 project, should it also be usable as a dependency?
Probably no change to the current practice, since the tck is intended
to be executed by itself with no user code involved.
2. Other issues
Action items from past meetings: Craig check into using the Apache
parent pom
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Jan 21, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
Dependencies have been changed to conform to the maven
DependencyManagement pattern.
Tck dependencies have been updated to the latest DataNucleus version
2.2.2. The dependency should actually be on the exectck project not
the tck project.
To run the tck with an IUT, users will have to edit the pom and
profiles to add their dependent jar files.
The "run-once" tests run twice. Is this ok? Yes.
2. Inheritance strategy http://mail-archives.apache.org/mod_mbox/db-jdo-dev/201101.mbox/browser
Surprising to hear that JPA has a mapping feature that JDO doesn't.
Maybe there is a misunderstanding. AI everyone: Is this scenario
really not supported by JDO?
3. Test case failure: SQLException in
ParenthesesMarkOperatorPrecedence https://issues.apache.org/jira/browse/JDO-672
No progress.
4. Other issues
Dependencies on JPA: the api needs JPA 3.0 and the tck needs JPA 2.0
The issue is with the getProperties() method in
JDOEntityManagerFactory which extends both EntityManagerFactory and
PersistenceManagerFactory. In JDO PersistenceManagerFactory the method
returns Properties and in JPA EntityManagerFactory returns Map<String,
Object>.
Possible solutions: change JDO PersistenceManagerFactory to return
Map<String, Object> or remove the JDOEntityManagerFactory and
JDOEntityManger interfaces. Are these being used by anyone?
AI Michael file a JIRA.
Action Items from weeks past:
[Jan 14 2011] Craig check into using the Apache parent pom. No progress.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Feb 4, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Craig
Russell
Agenda:
1.Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
There is now a profile to run the tck. To run the tck, run mvn
integration-test. Need to add sub-modules to the parent pom. Upgrade
pom to the latest Derby 10.7.1.1.
It would be good to be able to run the tck on an IUT simply by adding
a profile to the user's settings.xml and not require any changes to
the distributed api, tck, or exectck.
2. Inheritance strategy that results in a table per class... https://issues.apache.org/jira/browse/JDO-674
Seems like proposal 1 doesn't limit what we can do in the future, and
it's a good proposal. AI Craig update the JIRA.
3. Change JPA API dependency to org.eclipse.persistence https://issues.apache.org/jira/browse/JDO-675
There is no official javax.persistence. There is no
org.eclipse.persistence for maven 1. Propose postponing this change
until we leave maven 1. AI Michael update the JIRA.
4. Using Apache parent POM http://www.apache.org/dev/publishing-maven-artifacts.html
, https://issues.apache.org/jira/browse/MPOM
We can start by just adding the Apache parent pom and then the rest
can be added as we work to publish a release.
5. Other issues
Multi-tenancy (cloud) may be a good feature to consider for a future
release. May be similar to openjpa slices?
Use cases as an extension to fetch plan may be a good feature to
consider for a future release. AI Matthew write up a JIRA.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Feb 25, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Typesafe ... query capability for JDOQL - ready for check-in?. https://issues.apache.org/jira/browse/JDO-652
We need more people than have looked at this to take a closer look.
Volunteers? Michael, Craig. In particular, look at the TCK tests where
we run the queries twice: once with String-based and one with the API.
Adding a third option for the typesafe query would expose differences,
mismatches.
http://www.datanucleus.org/products/accessplatform/jdo/jdoql_typesafe.html
http://datanucleus.blogspot.com/2010/11/jdo-typesafe-vs-jpa-criteria.html
2. Inheritance strategy that results in a table per class - patch
provided. https://issues.apache.org/jira/browse/JDO-674
The patch looks good. Ok to check in.
3. Other issues
Dependency on JPA: The JIRA 675 to change tck pom dependency from
Geronimo to Eclipse. Won't fix. There's no need.
Maven2 upgrade: Once we have it all working, we will remove the maven1
support completely.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Mar 11, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Reminder: Next week the US will be on Daylight Savings Time.
Attendees: Michael Bouschen, Michelle Caisse, Matthew Adams, Craig
Russell
Agenda:
1. Maven 2 upgrade - using setting.xml or profiles.xml for iut profile https://issues.apache.org/jira/browse/JDO-647
Try using a property like <tck.iut.classpath> in the exectck to set up
the class path.
2. Typesafe ... query capability for JDOQL. https://issues.apache.org/jira/browse/JDO-652
A few method and class name issues that we should discuss and resolve.
Quickly, please.
3. Ability to mark a class as read-only - https://issues.apache.org/jira/browse/JDO-677
Probably doing the check on flush is better.
4. query improvements: downcasting
There don't seem to be any issues here. Just need spec update and TCK
test.
5. Other issues
Action Items from weeks past:
[Feb 25 2011] AI Michael, Craig, other volunteers: Look at
Typesafe ... query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Mar 4, 9 am Pacific Time
Posted by Andy Jefferson <an...@datanucleus.org>.
> 2. Typesafe ... query capability for JDOQL - ready for check-in?.
> https://issues.apache.org/jira/browse/JDO-652
> Some questions: the factory for query instances: should it be PM or
> PMF? Hint: do you really need to have the PM available in order to
> build a query? The PM represents your current connection to the
> database; the PMF represents the object model and mapping.
To build a query you don't need the PM (but then to create a javax.jdo.Query
object you don't really need a PM either :-P). To execute a
(Query/)TypesafeQuery/TypedQuery you need a PM, and if you put constructor on
the PMF then you have to pass the PM into the executeXXX methods.
> Is there a bug in the blog?
Yes there was, fixed thx.
> JDO-678 Set properties on PersistenceManager
> Seems like a good idea. Patch?
Will do.
Regards
--
Andy
DataNucleus (http://www.datanucleus.org)
Re: Minutes: JDO TCK Conference Call Friday, Mar 4, 9 am Pacific
Time
Posted by Michelle Caisse <mc...@sonic.net>.
On 03/04/2011 11:02 AM, Craig L Russell wrote:
> ...
>
> 1. Maven 2 upgrade - using setting.xml or profiles.xml for iut profile
> https://issues.apache.org/jira/browse/JDO-647
>
> Apparently maven doesn't want to encourage items in the settings.xml
> to affect the build, but we do. Specifically, we want to have the
> user's settings.xml to provide settings to run the iut. Any suggestions?
>From
http://maven.apache.org/guides/introduction/introduction-to-profiles.html:
> Profiles specified in external files (i.e in settings.xml or
> profiles.xml) are not portable in the strictest sense. Anything
> that seems to stand a high chance of changing the result of the
> build is restricted to the inline profiles in the POM. Things like
> repository lists could simply be a proprietary repository of
> approved artifacts, and won't change the outcome of the build.
> Therefore, you will only be able to modify the <repositories> and
> <pluginRepositories> sections, plus an extra <properties> section.
>
> The <properties> section allows you to specify free-form key-value
> pairs which will be included in the interpolation process for the
> POM. This allows you to specify a plugin configuration in the form
> of ${profile.provided.path}.
>
I don't understand what they are suggesting be done with a
${profile.provided.path} property.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Mar 4, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Maven 2 upgrade - using setting.xml or profiles.xml for iut profile https://issues.apache.org/jira/browse/JDO-647
Apparently maven doesn't want to encourage items in the settings.xml
to affect the build, but we do. Specifically, we want to have the
user's settings.xml to provide settings to run the iut. Any suggestions?
2. Typesafe ... query capability for JDOQL - ready for check-in?. https://issues.apache.org/jira/browse/JDO-652
Some questions: the factory for query instances: should it be PM or
PMF? Hint: do you really need to have the PM available in order to
build a query? The PM represents your current connection to the
database; the PMF represents the object model and mapping.
Also, the name sounds too "inside". Matthew made a similar comment.
I'd like to look at the name: "TypesafeQuery".
Is there a bug in the blog?
List<Object[]> results =
em.createQuery(criteria).getSingleResult(); // should return Object[]?
List<Integer> result =
tq.filter(cand.name.eq("MP3
Extra")).executeResultUnique(Integer.class, cand.value.max()); //
should return Integer?
Method name for returning projection might not be obvious.
Started looking at it in detail with an eye to including in 3.1. Not
done yet.
3. Ability to mark a class as read-only - https://issues.apache.org/jira/browse/JDO-677
Seems like a good idea. Anyone else have comments?
Where would an error be identified? At the time the user modifies a
persistent field? Or defer checking until flush (or commit)?
Portable behavior would probably mean defer checking.
Silently ignoring an update is probably not the right behavior.
4. Other issues
JDO-678 Set properties on PersistenceManager
Seems like a good idea. Patch?
Action Items from weeks past:
[Feb 25 2011] AI Michael, Craig, other volunteers: Look at
Typesafe ... query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Mar 11, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, March 11, at 9 am Pacific Time
to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven 2 upgrade - using setting.xml or profiles.xml for iut profile
https://issues.apache.org/jira/browse/JDO-647
2. Typesafe ... query capability for JDOQL.
https://issues.apache.org/jira/browse/JDO-652
3. Ability to mark a class as read-only -
https://issues.apache.org/jira/browse/JDO-677
4. query improvements: downcasting
5. Other issues
Action Items from weeks past:
[Feb 25 2011] AI Michael, Craig, other volunteers: Look at Typesafe ...
query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652
-- Michelle
JDO TCK Conference Call Friday, Mar 4, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, March 4, at 9 am Pacific Time
to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven 2 upgrade - using setting.xml or profiles.xml for iut profile
https://issues.apache.org/jira/browse/JDO-647
2. Typesafe ... query capability for JDOQL - ready for check-in?.
https://issues.apache.org/jira/browse/JDO-652
3. Ability to mark a class as read-only -
https://issues.apache.org/jira/browse/JDO-677
4. Other issues
Action Items from weeks past:
[Feb 25 2011] AI Michael, Craig, other volunteers: Look at Typesafe ...
query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652
-- Michelle
JDO TCK Conference Call Friday, Feb 25, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, February 25, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Typesafe ... query capability for JDOQL - ready for check-in?.
https://issues.apache.org/jira/browse/JDO-652
2. Inheritance strategy that results in a table per class - patch
provided. https://issues.apache.org/jira/browse/JDO-674
3. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Feb 4, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, February 4, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1.Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Inheritance strategy that results in a table per class...
https://issues.apache.org/jira/browse/JDO-674
3. Change JPA API dependency to org.eclipse.persistence
https://issues.apache.org/jira/browse/JDO-675
4. Using Apache parent POM
http://www.apache.org/dev/publishing-maven-artifacts.html,
https://issues.apache.org/jira/browse/MPOM
5. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Jan 28, 9 am Pacific Time
Posted by Craig L Russell <cr...@ORACLE.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1.Interface JDOEntityManagerFactory does not compile with JPA. https://issues.apache.org/jira/browse/JDO-673
I propose that we remove the two interfaces JDOEntityManagerFactory
and JDOEntityManager from the 3.1 release. This is a backward
compatibility issue but never worked with the published JPA 2.0
specification. Since it is impossible to instantiate a class
implementing this interface, it probably is not an issue.
Any objections to removing these two interfaces?
2. Other issues
- Is another mapping needed to cover the JPA Table-per-concrete-class?
See
http://www.datanucleus.org/products/accessplatform_3_0/jdo/orm/inheritance.html
The standard JDO mapping strategies do not cater for concrete
subclasses of concrete superclasses being mapped with both concrete
classes having all fields mapped.
AI: Andy file a JIRA. Seems like a good idea. Need to define exactly
the semantics of having a subclass of a class that is mapped as
complete-table. Can the subclass be mapped as new-table (all new
fields are mapped to the new table), subclass-table (no table is
defined, subclasses must have their fields mapped by the superclass),
superclass-table (no table is defined, all new fields are mapped in
the existing table).
- We should take a look at jsr 338 to see if there are any good ideas
that we can adopt.
- https://issues.apache.org/jira/browse/JDO-672 has had no response yet.
Action Items from weeks past:
[Jan 14 2011] Craig check into using the Apache parent pom
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Jan 28, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, January 28, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1.Interface JDOEntityManagerFactory does not compile with JPA.
https://issues.apache.org/jira/browse/JDO-673
2. Other issues
Action Items from weeks past:
[Jan 14 2011] Craig check into using the Apache parent pom
[Jan 21 2011] AI everyone: Is TABLE_PER_CLASS really not supported by JDO?
-- Michelle
JDO TCK Conference Call Friday, Jan 21, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, January 21, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Inheritance strategy
http://mail-archives.apache.org/mod_mbox/db-jdo-dev/201101.mbox/browser
3. Test case failure: SQLException in ParenthesesMarkOperatorPrecedence
https://issues.apache.org/jira/browse/JDO-672
4. Other issues
Action Items from weeks past:
[Jan 14 2011] Craig check into using the Apache parent pom
-- Michelle
JDO TCK Conference Call Friday, Jan 14, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, January 14, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, January 7, at 9 am Pacific Time
to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
-- Michelle
NO JDO TCK Conference Call Friday, Dec 24
Posted by Michelle Caisse <mc...@sonic.net>.
JDO is on winter break. Next meeting: January 7, 2011
-- Michelle
JDO TCK Conference Call Friday, Dec 17, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, December 17, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Avg return type - patch available for review
https://issues.apache.org/jira/browse/JDO-643
3. Extend PersistenceManageFactory to return all known entity classes
-new comments https://issues.apache.org/jira/browse/JDO-667
4. Other issues
Action Items from weeks past:
-- Michelle
Re: JDO TCK Conference Call Friday, Dec 10, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Hi,
Sorry I'll be in a plane during the call. Enjoy the call.
Craig
On Dec 9, 2010, at 7:02 PM, Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, December 10, at 9 am
> Pacific Time to discuss JDO TCK issues and status.
>
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Dec 10, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, December 10, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Dec 3, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Craig
Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
Good progress. No hang any longer. Getting the schema loaded. But not
quite working yet. Some tables are not created. Signature test
complains.
2. Other issues
There's a project called naked objects which is now incubating as
Apache Isis. How about a JDO store for the objects?
Check it out: https://issues.apache.org/jira/browse/ISIS-14
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!