Remove keyword IMPORTS from TCK query test classes
--
Key: JDO-305
URL: http://issues.apache.org/jira/browse/JDO-305
Project: JDO
Type: Bug
Components: tck20
Versions: JDO 2 beta
Reporter: Michael
Hi Andy,
Hi Craig,
In section 14.4 we have IMPORTS/imports specified twice in the list of
keywords. Not only that but in Section 24 we no longer have IMPORTS. Think it
needs removing from 14.4.
Good catch! Yes, IMPORTS/imports need to be removed from the list of
JDOQL keywords in section
How can I get the latest pdf of the spec ?
--
Karan Singh
Hi Craig,
I am sorry, but I dont know where to go to get the pdf.
Craig L Russell wrote:
Hi Karan,
When prompted for user name and password, use your jira login and
password.
Regards,
Craig
On Feb 14, 2006, at 6:07 AM, karan malhi wrote:
How can I get the latest pdf of the spec ?
--
Hi Karan,
try http://access1.sun.com/jdo/private/index.html
Regards Michael
Hi Craig,
I am sorry, but I dont know where to go to get the pdf.
Craig L Russell wrote:
Hi Karan,
When prompted for user name and password, use your jira login and
password.
Regards,
Craig
On Feb 14, 2006,
[ http://issues.apache.org/jira/browse/JDO-305?page=all ]
Michael Bouschen updated JDO-305:
-
Attachment: JDO-305.patch
The attached patch JDO-305.patch for review fixes the two classes
SingleStringQuery and QueryElementHolder and removes the 'IMPORTS'
Javadogs,If none of the implementations supports projections of collections or maps, we can simply disallow it. If some do support it, we can say it's not portable.For now, I'll propose disallowing it, and if there are implementations out there we can change to non-portable.proposal
Hi Andy,
Here's a proposal for review.
I can't see the value in having the table attribute for embedded
index or unique elements. But if they are defined at the class or
interface level, the table would be used to identify an index or
unique constraint on an associated table (secondary
