You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2007/02/15 21:55:05 UTC
[jira] Created: (DERBY-2341) derby.language.statementCacheSize is
ignored when it is set as a database property.
derby.language.statementCacheSize is ignored when it is set as a database property.
-----------------------------------------------------------------------------------
Key: DERBY-2341
URL: https://issues.apache.org/jira/browse/DERBY-2341
Project: Derby
Issue Type: Bug
Components: SQL
Affects Versions: 10.3.0.0
Reporter: Daniel John Debrunner
Assigned To: Daniel John Debrunner
Priority: Minor
Fix For: 10.3.0.0
Found during the converson of the statement caching tests to JUnit DERBY-2332.
Looking at the trunk and 10.2 it seems to be a regression in 10.3 causes by DERBY-2138 (mea culpa).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-2341) derby.language.statementCacheSize is
ignored when it is set as a database property.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel John Debrunner closed DERBY-2341.
----------------------------------------
Resolution: Fixed
Committed revision 508163. checked with new test for DERBY-2332 (to be committed soon).
> derby.language.statementCacheSize is ignored when it is set as a database property.
> -----------------------------------------------------------------------------------
>
> Key: DERBY-2341
> URL: https://issues.apache.org/jira/browse/DERBY-2341
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> Found during the converson of the statement caching tests to JUnit DERBY-2332.
> Looking at the trunk and 10.2 it seems to be a regression in 10.3 causes by DERBY-2138 (mea culpa).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.