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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2018/08/07 03:12:00 UTC

[jira] [Updated] (DERBY-7006) Investigate putting generated classes under the engine module loader

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

Rick Hillegas updated DERBY-7006:
---------------------------------
    Urgency: Normal

> Investigate putting generated classes under the engine module loader
> --------------------------------------------------------------------
>
>                 Key: DERBY-7006
>                 URL: https://issues.apache.org/jira/browse/DERBY-7006
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.15.0.0
>            Reporter: Rick Hillegas
>            Priority: Major
>
> Right now, the generated query plans are compiled into the catch-all unnamed module. This forces us to grant reflective access to several engine packages. It would be nice to encapsulate the generated classes inside the engine module loader.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)