[ 
https://issues.apache.org/jira/browse/CAY-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrus Adamchik updated CAY-1470:
---------------------------------
    Fix Version/s:     (was: 2.0.5)

> Oracle: Problem with bind CHAR in select
> ----------------------------------------
>
>                 Key: CAY-1470
>                 URL: https://issues.apache.org/jira/browse/CAY-1470
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 2.0 branch, 3.0
>            Reporter: Evgeny Ryabitskiy
>            Assignee: Evgeny Ryabitskiy
>            Priority: Critical
>              Labels: 3.1-review
>             Fix For: Undefined future
>
>         Attachments: CAY-1470-Test.patch, CAY-1470.patch, CAY-1470.patch, 
> CAY-1470.patch
>
>
> I have Table tUser
> desc tUser
> Name                           Null                Type                       
>                                                                               
>                                                                               
>        
> ------------------------------ -------- 
> USERID                         NOT NULL NUMBER(15)                            
>                                                                               
>                                                                           
> BRIEF                             NOT NULL CHAR(30)   
> And wish to find user with BRIEF 'credit' :
> INFO  QueryLogger: Detected and installed adapter: 
> org.apache.cayenne.dba.oracle.OracleAdapter
> INFO  QueryLogger: SELECT * FROM tUser WHERE Brief = ? [bind: 'credit']
> INFO  QueryLogger: === returned 0 rows. - took 125 ms.
> But if I try whitespaces at the end I would get:
> INFO  QueryLogger: SELECT * FROM tUser WHERE Brief = ? [bind: 'credit         
>                ']
> INFO  QueryLogger: === returned 1 row. - took 109 ms.
> It's absolutely not CROSS DB behavior!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to