db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2408) Coversion from string to time/date/timestamp does not use the locale because context pushing does not happen for PreparedStatement.setXXX methods
Date Tue, 06 Mar 2007 19:55:24 GMT
Coversion from string to time/date/timestamp does not use the locale because context pushing
does not happen for PreparedStatement.setXXX methods
-------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: DERBY-2408
                 URL: https://issues.apache.org/jira/browse/DERBY-2408
             Project: Derby
          Issue Type: Bug
          Components: JDBC
    Affects Versions: 10.2.2.0, 10.2.1.6, 10.1.3.1, 10.1.2.1, 10.1.1.0, 10.0.2.1, 10.0.2.0
            Reporter: Mamta A. Satoor


In the Derby implementation, the JDBC setXXX methods on PreparedStatement does not push/pop
the context manager. This is to prevent the driver from getting performance hit. But some
of the setXXX methods like, SQLTimestamp.setValue(String theValue), SQLTime.setValue(String
theValue), SQLDate.setValue(String theValue) look at the context manager to find out the locale
of the database so they can use that locale to do the appropriate conversion from string to
date/time/timestamp. But since there is no context setup done for setXXX methods, locale information
can't be established by these methods and they do not use the correct locale. This behavior
has been around all Derby releases.

More information on this can be found in following thread http://www.nabble.com/PreparedStatement.setXXX-methods-do-not-set-up-ContextStack.-Is-that-right-and-if-so%2C-why--tf3337937.html#a9283354

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


Mime
View raw message