Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Date: Fri, 11 Mar 2011 04:16:59 +0000 (UTC)
From: "Matthew T. Adams (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Message-ID: 
 <1459107519.12603.1299817019374.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Created: (JDO-679) Clarify downcasts in queries
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Clarify downcasts in queries
----------------------------

                 Key: JDO-679
                 URL: https://issues.apache.org/jira/browse/JDO-679
             Project: JDO
          Issue Type: Improvement
          Components: specification
    Affects Versions: JDO 3 maintenance release 1
            Reporter: Matthew T. Adams


The specification needs clarification when it comes to downcasting within the query filter.  Currently, the JDO 3.0 specification states (14.6.2):
"Navigation through a null-valued field, which would throw NullPointerException, is treated as if the subexpression returned false. Similarly, a failed cast operation, which would throw ClassCastException, is treated as if the subexpression returned false. Other subexpressions or other values for variables might still qualify the candidate instance for inclusion in the result set."

The clarification is that if a cast will never be successful (casting Employee as Integer, for example), then an exception should be thrown (JDOUserException with an inner ClassCastException?), otherwise, the cast behaves as the specification dictates.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira