The subselect would return 88 and then the outer select would become
"SELECT FROM " + OptionalSample.class.getName() + " WHERE " +
“(88) == id”;
Seems to me this should select the object whose id is 88.
Craig
> On Sep 24, 2016, at 9:22 AM, Tilmann <zaesc...@gmx.de> wrote:
>
> Hi,
>
> could I get some feedback?
>
> I tried the following subquery:
>
> "SELECT FROM " + OptionalSample.class.getName() + " WHERE " +
> "(select max(a.id) from " + OptionalSample.class.getName() +
> " a " +
> "where a.optionalPC != null) == id";
>
> This returns '88' (an integer) instead of the object with id==88. Is this
> expected to return an integer?
>
> Full code (can be used in SupportedOptionalMethods.java):
> String singleStringJDOQL2 =
> "SELECT FROM " + OptionalSample.class.getName() + " WHERE " +
> "(select max(a.id) from " + OptionalSample.class.getName() +
> " a " +
> "where a.optionalPC != null) == id";
> Object[] expectedResult2 = new Object[]{oidReferencedPC1};
> // single String JDOQL
> Query singleStringQuery2 = pm.newQuery(singleStringJDOQL2);
> executeJDOQuery(ASSERTION_FAILED, singleStringQuery2,
> singleStringJDOQL2,
> false, null, expectedResult2, true);
>
>
> Kind regards,
> Tilmann
>
>
> On 22.09.2016 22:33, Michael Bouschen wrote:
>> Hi,
>>
>> We will have our regular meeting Friday, September 23 at 9 AM Pacific
>> Daylight Time (PDT) to discuss JDO TCK issues and status.
>>
>> We use the new dial-in for audio and video. You need a Skype account to join.
>> https://join.skype.com/euV54RJwJBcf
>>
>> Agenda:
>> 1. JIRA JDO-756 "Enhance PK to avoid LongIdentity/StringIdentity
>> dependencies" https://issues.apache.org/jira/browse/JDO-756
>> 2. Spec changes for JDO-751 "Support for Java8 Optional"
>> https://issues.apache.org/jira/browse/JDO-751
>> 3. JDO-735 "Make PersistenceManager and Query support AutoCloseable
>> (JDK1.7+)" https://issues.apache.org/jira/browse/JDO-735
>> 4. JDO-747 "Behavior of delete() with multiple concurrent Transactions"
>> https://issues.apache.org/jira/browse/JDO-747
>> 5. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to
>> prepare JCP Change Log
>> 6. Other issues
>>
>> Action Items from weeks past:
>> [Oct 30 2015] AI Craig: File a maintenance review with JCP
>> [May 15 2015] AI Craig Spec change for roll back an active transaction when
>> closing a persistence manager (JDO-735)
>> [Apr 17 2015] AI Craig: Oracle spec page on JDO need to be updated once the
>> JCP Maintenance Release for JDO 3.1 is published
>> [Oct 17 2014] AI Matthew any updates for "Modify specification to address
>> NoSQL datastores": https://issues.apache.org/jira/browse/JDO-651?
>> [Feb 28 2014] AI Everyone: take a look at
>> https://issues.apache.org/jira/browse/JDO-712
>> [Feb 28 2014] AI Everyone: take a look at
>> https://issues.apache.org/jira/browse/JDO-625
>> [Dec 13 2013] AI Craig file a JIRA for java.sql.Blob and java.sql.Clob as
>> persistent field types
>> [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about
>> JDOHelper methods. In process.
>>
>> Regards Michael
>>
>>
>
Craig L Russell
Architect
craig.russ...@oracle.com
P.S. A good JDO? O, Gasp!
