[
https://issues.apache.org/jira/browse/DERBY-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305083#comment-17305083
]
Bryan Pendleton commented on DERBY-7108:
----------------------------------------
In a query such as "SELECT LAST_NAME,MANAGER FROM EMPLOYEE WHERE FIRST_NAME =
'BRYAN'", the generated code implements behaviors such as
* Project (extract just the LAST_NAME and MANAGER columns from the row)
* Restrict (execute the comparison to check if the FIRST_NAME column equals
"BRYAN")
So we generally don't know these details until the query is actually just ready
to be executed, since the SQL statements arrive dynamically over the JDBC
connection, and the specific values in the restriction can be set via '?'
parameters in PreparedStatements, etc.
> Make derby graalvm friendly
> ---------------------------
>
> Key: DERBY-7108
> URL: https://issues.apache.org/jira/browse/DERBY-7108
> Project: Derby
> Issue Type: Task
> Affects Versions: 10.16.0.0
> Reporter: Romain Manni-Bucau
> Priority: Major
> Attachments: outs.zip
>
>
> Hi,
> It would be neat to be able to use derby embedded with graalvm.
> Some work started at [https://github.com/apache/geronimo-arthur/tree/openjpa]
> (see [https://www.mail-archive.com/dev@geronimo.apache.org/msg97748.html)]
> but I faced some weird issue about derby context.
> Wonder how derby community considers graalvm (h2 for example explicitly said
> it will never care about it and is happy with having broken graal support in
> a minor version which is their choice but also means there is no point
> integrating it since work can be to redo for each minor).
> If you are interested I'm happy to collaborate if needed to try to make it
> supported through arthur or native native-image configuration (can sit in the
> derby jar to work OOTB too).
> Side note: if it helps we can chat on asf slack.
> Romain
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
