Hi Erik,do you think we need to support super in JDOQL? You only need it if the cancdidate class hides a supeclass field and if S is the superclass you can write 'super.field' as '((S)this).field'.Regards MichaelCraig,In JDOQL BNF, it's not a valid field accessor. The same for ClassName.superCurrent-------FieldAccess:FieldNamePrimary . FieldNameRegards,Erik BengtsonQuoting Craig L Russell <Craig.Russell@Sun.COM>:
Hi Erik,It is not in the spec because it's already a Java keyword. Please see14.4:KeywordsKeywords must not be used as package names, class names, parameternames, or variable names in queries. Keywords are permitted as fieldnames only if they are on the right side of the “.” in field accessexpressions as defined in the Java Language Specification secondedition, section 15.11. Keywords include the Java language keywordsand the JDOQL keywords. Java keywords are as defined in the Javalanguage specification section 3.9, plus the boolean literals trueand false, and the null literal. JDOQL keywords maybe written in alllower case or all upper case.What specifically are you interested in knowing?Regards,CraigOn Jan 7, 2006, at 3:57 PM, firstname.lastname@example.org wrote:
Hi,Is it intentionally not in the spec?Regards,Erik Bengtson
Craig RussellArchitect, Sun Java Enterprise System http://java.sun.com/products/jdo408 276-5638 mailto:Craig.Russell@sun.comP.S. A good JDO? O, Gasp!
--Michael Bouschen Tech@Spree Engineering GmbHmailto:email@example.com http://www.tech.spree.de/Tel.:++49/30/235 520-33 Buelowstr. 66Fax.:++49/30/2175 2012 D-10783 Berlin
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!