[
https://issues.apache.org/jira/browse/DERBY-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791882#action_12791882
]
Shazin Sadakath commented on DERBY-4467:
----------------------------------------
Hi Rick,
What I have done thus far was working on an idea to make Derby as friendly as
possible to non Java Developers thus enabling
derby to reach a large no of developers. As a solution for that I have just
brought forward this.
I have already gone through what are the changes necessary to enabling
declaring of these sort of Stored Routines but I haven't implemented yet.
That is because I knew that my idea would also have a lot of disadvantages just
as the one Dag pointed out.
Anyway I will try my best to implement what you asked and submit so that you
can decide what needs to done.
Thanks,
Shazin
> Non Java Stored Routines Using Java Scripting API
> -------------------------------------------------
>
> Key: DERBY-4467
> URL: https://issues.apache.org/jira/browse/DERBY-4467
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Environment: Windows XP, Java 1.6
> Reporter: Shazin Sadakath
> Priority: Minor
> Attachments: DDL.sql, DerbyStoredRoutine.zip, ScreenShot.JPG
>
>
> I have been working on an idea that lets you create Stored Procedures using
> languages other than Java with a perspective of Apache Derby as a Network
> Server. I tried this by using Sun Java Scripting API for JRE 1.6+ and Apache
> BSF http://jakarta.apache.org/bsf/ for JRE 1.4+.
> This has certain advantages when it comes to compiled java stored routines.
> 1. It is dynamic.
> 2. Requires no configuration of classpath.
> 3. Requires no use of SQLJ.INSTALL_JAR and SQLJ.REPLACE_JAR.
> 4. Very easy to maintain
> 5. Allows the use of Sun Java Runtime Library via Object Binding.
> 6. Supports JavaScript, Jython, Dynamic Java and many more scripting
> languages. https://scripting.dev.java.net/
> 7. No need of introducing a new SQL/PSM grammar to the current SQLParser.
> There are two approaches for this enhancement.
> 1. Having this as an external utility component such as ij, dblooks
> 2. Having this as a built in feature.
> I have done this in the former method for demonstration purpose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
