You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Daniele Valentini (JIRA)" <ib...@incubator.apache.org> on 2007/12/04 09:36:43 UTC

[jira] Created: (IBATIS-473) see IBATIS-78

see IBATIS-78
-------------

                 Key: IBATIS-473
                 URL: https://issues.apache.org/jira/browse/IBATIS-473
             Project: iBatis for Java
          Issue Type: Bug
          Components: DAO
    Affects Versions: 2.3.0
         Environment: JVM 1.5 with Spring Trasaction
            Reporter: Daniele Valentini
            Priority: Critical


I've read a bug (2005) IBATIS-78 that there is a problem with JDBC Driver Oracle when the select staement is a follow:

"select * from [tableName] where [fieldName]=#value#"

where a fieldName is defined a CHAR(10) type and the parameter passed (value) is a java.lang.String type.
if the parameter is : "ABCD      " the record found it! and if parameter is : "ABC" the records not found!.


I use a class JDBC : oracle.jdbc.pool.OracleDataSource present in the jar file named ojdbc14.jar (Oracle 10.2g)
The fix present in precedent Bug say that the problem is  present with a DBCP (BasicDataSource) 
The problem is very critical for my Project .
How to ?????

I've read also that the property the DataSource Driver.fixedString imposted a true value but the property in my class JDBC (oracle.jdbc.pool.OracleDataSource) not is present 

PS. i use in jndi for localized a dataSource in my Server WAS 6.1 but the problem is present also in Junit Test without a server .




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


[jira] Closed: (IBATIS-473) see IBATIS-78

Posted by "Jeff Butler (JIRA)" <ib...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/IBATIS-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Butler closed IBATIS-473.
------------------------------

    Resolution: Invalid

Several things...

1. Use the mailing lists for support questions
2. This is not a bug in iBATIS - it's that way databases work!  This is why it's better to use VARCHAR than CHAR in many cases.
3. The bug you reference was simply a way to forward an Oracle specific driver property during configuration.  This is not applicable in your situation because you are using JNDI.
4. You need to configure your JNDI datasource to add the Oracle driver property "fixedString=true".  This is done in the WebSphere console - not in iBATIS.
5. For your JUNIT tests, you need to configure iBATIS differently - using either SIMPLE or DBCP data sources and setting the property as shown in IBATIS-78


> see IBATIS-78
> -------------
>
>                 Key: IBATIS-473
>                 URL: https://issues.apache.org/jira/browse/IBATIS-473
>             Project: iBatis for Java
>          Issue Type: Bug
>          Components: DAO
>    Affects Versions: 2.3.0
>         Environment: JVM 1.5 with Spring Trasaction
>            Reporter: Daniele Valentini
>            Priority: Critical
>
> I've read a bug (2005) IBATIS-78 that there is a problem with JDBC Driver Oracle when the select staement is a follow:
> "select * from [tableName] where [fieldName]=#value#"
> where a fieldName is defined a CHAR(10) type and the parameter passed (value) is a java.lang.String type.
> if the parameter is : "ABCD      " the record found it! and if parameter is : "ABC" the records not found!.
> I use a class JDBC : oracle.jdbc.pool.OracleDataSource present in the jar file named ojdbc14.jar (Oracle 10.2g)
> The fix present in precedent Bug say that the problem is  present with a DBCP (BasicDataSource) 
> The problem is very critical for my Project .
> How to ?????
> I've read also that the property the DataSource Driver.fixedString imposted a true value but the property in my class JDBC (oracle.jdbc.pool.OracleDataSource) not is present 
> PS. i use in jndi for localized a dataSource in my Server WAS 6.1 but the problem is present also in Junit Test without a server .

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