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

Kathey Marsden commented on DERBY-3676:
---------------------------------------

In terms of compatibility,  I think it is fine to change the format of 
toString() as long as 
1)  It still includes the old information (e.g. the identifier of the compiled 
plan.)
2) It is easily to parse.
3) We include a release note.

i don't think we are bound to the exact format of toString() and it is not part 
of the API contract.  I  think it is just typically used as a tool for 
diagnostics.  Since users are dealing with the PreparedStatement interface in 
typical usage, a new method would likely not be all that helpful as they would 
need to use reflection or cast to the internal Derby classes and probably would 
not know that such a method exists to help them in normal usage.  



> Make the toString() method of Derby PreparedStatements print out SQL text 
> with ? parameters replaced by the values that have been set so far
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3676
>                 URL: https://issues.apache.org/jira/browse/DERBY-3676
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>            Reporter: Rick Hillegas
>            Assignee: Siddharth Srivastava
>         Attachments: humanstringprepared.txt, humanstringprepared.txt, 
> humanstringprepared.txt, humanstringprepared.txt, humanstringprepared.txt, 
> humanstringprepared.txt, humanstringprepared.txt, ick.txt, ick.txt, 
> prepared.diff, statementCacheVTI.sql
>
>
> This topic came up in the following email thread on the user list: 
> http://www.nabble.com/PreparedStatement.toString%28%29---nice-formatting-td17250811.html#a17250811
>  Here's what the thread requests: 
> "In mysql, a toString() on a PreparedStatement will do this, eg "select x
> from foo where x.a = ?" will become "select x from foo where x.a = 1" with
> the appropriate setValue() call."
> At first blush, this seems like it might be a simple project for a newcomer.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to