Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <5678150.1178301255329.JavaMail.jira@brutus>
Date: Fri, 4 May 2007 10:54:15 -0700 (PDT)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2606) Derby should print the parameters to
 failed statements to the derby.log when it logs the error
In-Reply-To: <6009228.1178228175282.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden updated DERBY-2606:
----------------------------------

    Attachment: DERBY_2606_diff.txt

attaching a patch to print parameter info to derby.log with error reporting.  I agree with Mike that there is already exposure for encrypted databases when the data is part of the statement, so I think that it should be ok to go ahead and commit this patch.   Please let me know if you have objections.  Otherwise I will commit this afternoon.  I did not add a test case because it is a little awkward to parse the log file.  If someone thinks I should add one, please let me know that too.

> 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
>         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.