[jira] Commented: (DERBY-2606) Derby should print the parameters to failed statements to the derby.log when it logs the error

["Daniel John Debrunner (JIRA)" <ji...@apache.org>]

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

Daniel John Debrunner commented on DERBY-2606:
----------------------------------------------

For encrypted databases this would be an issue because the error log is not encrypted, so having user values appear in the log in clear could be undesirable.

> Derby should print the parameters to failed statements to the derby.log when it logs the error 
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2606
>                 URL: https://issues.apache.org/jira/browse/DERBY-2606
>             Project: Derby
>          Issue Type: Improvement
>          Components: Services
>    Affects Versions: 10.3.0.0
>            Reporter: Kathey Marsden
>         Assigned To: Kathey Marsden
>            Priority: Minor
>
> It would be good if when derby dumped an error to derby.log it printed the parameters for the failed statement.  Currently the default behaviour is that only the statement text will print.  Users have to set  derby.language.logStatementText=true if they want to see the parameters.  It would be useful if any errors included the parameters as well as the statement text.
> To reproduce 
> put derby.stream.error.logSeverityLevel=0 in your derby.properties and run this script:
>  connect 'jdbc:derby:wombat;create=true';
> create table t (i int);
> prepare p as 'insert into t values(?)';
>  execute p using 'values(1)';
> execute p using 'values(10000000000000000000000000000000000000000000)';

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