Bug #1083 Java stored procedures would best meet our needs
Submitted: 18 Aug 2003 13:24 Modified: 21 Aug 2003 2:21
Reporter: Scott Ellsworth Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S4 (Feature request)
Version:5 OS:anpy
Assigned to: CPU Architecture:Any

[18 Aug 2003 13:24] Scott Ellsworth
Description:
I note in your documentation that you have not entirely nailed down how you intend to implement 
stored procedures.

For what we do, Java stored procedures best meet our needs.  We currently use both Java and PL/
SQL stored procedures for our biotech work.  As time is passing, we find that we are moving our 
procedures from PL/SQL to Java, despite the performance impact, as Java stored procedures have 
proved more maintainable over time.

On a related note, while views are handy for us, they are of lesser importance than Java stored 
procedures.

How to repeat:
This is a feature request, and thus is not possible right now

Suggested fix:
Add Java-based stored procedures when you get to version 5.1
[21 Aug 2003 2:21] Peter Zaitsev
Thank you for your feedback.

We do plan to have Java supported as stored procedure language, as well as few other languages, such as Perl, PHP.  

However in initial release we're planing to concentrate on ANSI SQL language stored procedures, as well as extension interface which would allow you to easily stick support for any language Stored procedures into MySQL.