db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-2606) Derby should print the parameters to failed statements to the derby.log when it logs the error
Date Fri, 04 May 2007 20:58:16 GMT

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

Kathey Marsden closed DERBY-2606.
---------------------------------


> 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
>             Fix For: 10.1.3.2, 10.2.2.1, 10.3.0.0
>
>         Attachments: d2602.java, DERBY_2606_diff.txt, DERBY_2606_stat.txt
>
>
> 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.


Mime
View raw message