Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
Message-ID: <868823250.1221052451845.JavaMail.jira@brutus>
Date: Wed, 10 Sep 2008 06:14:11 -0700 (PDT)
From: "Andrey Razumovsky (JIRA)" <dev@cayenne.apache.org>
To: dev@cayenne.apache.org
Subject: [jira] Created: (CAY-1105) Expressions in-memory automatic type
 convertion
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Expressions in-memory automatic type convertion
-----------------------------------------------

                 Key: CAY-1105
                 URL: https://issues.apache.org/cayenne/browse/CAY-1105
             Project: Cayenne
          Issue Type: Improvement
          Components: Cayenne Core Library
    Affects Versions: 3.0
            Reporter: Andrey Razumovsky
            Assignee: Andrus Adamchik
         Attachments: patch-test-Expr.txt

The root of the problem is difference in behavior of expressions on server (using queries) and in-memory (using Expression.match(...). All DBMS I know support automatic type convertion, i.e. if I write 
SELECT * FROM a WHERE intProperty='1'
everything will go OK.

So, if I write an expression like [note quotes at 1!]
ExpressionFactory.greaterExp("intProperty", "1")

it will go normally with a query, but will result in an exception if I try to invoke match(...).
I suggest to make the behavior similiar and therefore implement automatic type convertion on expressions. I've submitted a patch with a number of tests, which all fail. I think the must all succeed.

Comments and other expression improvement suggestions are welcomed

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.