You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Rick Curtis (JIRA)" <ji...@apache.org> on 2012/09/27 23:09:07 UTC

[jira] [Commented] (OPENJPA-2264) Upcast PreparedStatementManagerImpl.logSQLWarnings to take a Statement rather than a PreparedStatement

    [ https://issues.apache.org/jira/browse/OPENJPA-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465093#comment-13465093 ] 

Rick Curtis commented on OPENJPA-2264:
--------------------------------------

Committed revision 1388137 to trunk.
                
> Upcast PreparedStatementManagerImpl.logSQLWarnings to take a Statement rather than a PreparedStatement
> ------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-2264
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2264
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: jdbc, kernel
>    Affects Versions: 2.2.0, 2.3.0
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>            Priority: Minor
>             Fix For: 2.3.0, 2.2.1
>
>
> While writing a custom PreparedStatementManager I have a Statement that I want to pass to the org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.logSQLWarnings method, but that method incorrectly requires a PreparedStatement.
> With this JIRA I'm going to change the parameter type for this method to accept a Statement.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira