[
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,
the patch is virtually ready now; the toString() /idString() change that I
favour would need documenting;
the question of quoting substitutions needs addressing in more detail;
currently it quotes all values when Embedded, unquotes nulls from the client;
as well as improving the consistency, there are questions such as how to
substitute binary data, whether to unquote more types, etc;
it seems to me that DerbyPreparedStatement must be an Interface to allow the
multiple inheritance connection; currently I'm trying to see precisely what the
ants are doing :o) so it'll compile properly
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,
> 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.
