[
https://issues.apache.org/jira/browse/DERBY-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682177#comment-13682177
]
Rick Hillegas commented on DERBY-6259:
--------------------------------------
Thanks for voicing those concerns, Mike. I think we're still committed to
running Derby on small devices. That, at least, was the intent of all the work
Dag put into implementing the Compact Profile 2 DataSources in release 10.10.
+1 to running on Android too.
> Collapse the level 2 optimizer into its parent module.
> ------------------------------------------------------
>
> Key: DERBY-6259
> URL: https://issues.apache.org/jira/browse/DERBY-6259
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.11.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-6259-01-aa-collapseOptimizers.diff
>
>
> Right now there are 2 optimizer implementations, only one of which is ever
> loaded. The other implementation was disabled by the following comment in
> modules.properties:
> # use level1 optimizer for small configurations
> #
> # can't do this in the codeline because with 2 implementations, it is entirely
> # by chance which get picked. So we may be running with different modules
> # depending on which jdk
> #
> # to be resolve by Siuling and Dan
> #
> #derby.module.optimizerSmall=org.apache.derby.impl.sql.compile.OptimizerFactoryImpl
> #cloudscape.config.optimizerSmall=cloud,cloudtarget
> Since we have deprecated support for the small CDC configuration, I don't
> think that we need further resolution by Siuling and Dan. Collapsing the two
> optimizers together should slightly reduce our static footprint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
