[
https://issues.apache.org/jira/browse/DERBY-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-4771:
----------------------------
Attachment: rjall.out
Hi Kristian:
Thank you for doing such a great work. I am very interested of this
feature and would love to keep learning about this feature. The check for
container opened in read-only mode error behaves much better. I was wondering,
is it a good idea to check set a flag on PrepareStatement that possible allow
check about database status somewhere between generating PreparedStatement and
the time we check for exception in GenericStatement.java for store, lcc, tx or
something else? Could it help the situation we are in?
I did run the Suites.all test suits. This is for reference point only. I
got 6 failures. Four of them are all for lang.OrderByAndSortAvoidance except
testOSReadOnly is having permission problem when it try to remove directory:
c:\derby2\trunk\testallpackages\system\singleUse\readOnly or copy directory
from c:\derby2\trunk\testallpackages\system\singleUse\oneuse4e to
c:\derby2\trunk\testallpackages\system\singleUse\readOnly Hope this help!
> Continue investigation of automatic creation/update of index statistics
> -----------------------------------------------------------------------
>
> Key: DERBY-4771
> URL: https://issues.apache.org/jira/browse/DERBY-4771
> Project: Derby
> Issue Type: Task
> Reporter: Kristian Waagan
> Attachments: derby-4771-1a-prototype_code_dump.diff,
> derby-4771-1a-prototype_code_dump.stat,
> derby-4771-1b-prototype_code_dump.diff, rjall.out, rjall.out
>
>
> Work was started to improve Derby's handling of index statistics. This issue
> tracks further discussion and work for this task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
