[
https://issues.apache.org/jira/browse/DERBY-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark B updated DERBY-3676:
--------------------------
Attachment: humanstringprepared.txt
Hi Dag,
Understood :-)
so the newer implementation seems to work so far, though a touch less elegant
:D ; I notice that as a result of the way toString() is inherited, there's no
particular need for DerbyPreparedStatement after all, as long as people who
were accessing EmbedPreparedStatement.toString() now change to
EmbedPreparedStatement.idString(); unless it is felt appropriate to add the
idString() method to the client api?
Best regards
Mark
> 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
> Attachments: humanstringprepared.txt, humanstringprepared.txt,
> humanstringprepared.txt, ick.txt, ick.txt
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
