MySQL Gets Functions in Java 318
Java Coward writes "Eric Herman and MySQL's Brian "Krow" Aker have released code to allow the DBMS MySQL to run Java natively inside of the database. The code allows users to write functions inside of the database that can be then used in SELECT/INSERT/UPDATE statements. So when will someone do Ruby?"
Hmmmm (Score:5, Insightful)
My bad (Score:4, Insightful)
Re:Keep this out. (Score:4, Insightful)
The 'lusers' may not use this new feature but Java programmers will and hopefully will enjoy it.
Sounds like... (Score:3, Insightful)
I hope this isn't a "Hey wouldn't it be really neat!" feature. The last time that happened, someone at MS thought executable email would really neat.
That's great (Score:5, Insightful)
Re:Keep this out. (Score:5, Insightful)
1) Java isn't going to slow down any queries unless you use Java functions.
2) What do you care that someone else isn't smart enough to write good software?
3) MySQL as it stands has no other way to really embed functions easily, and it's actually more effecient to run code on the server and transfer data back afterwords.
Java in the DB - very, very bad idea (Score:3, Insightful)
Java is a nice programming language. Go write web apps, middleware, network software, desktop apps with it but not stored procedures.
Is mySQL process going to start the whole new JVM on every hit? Or VM is going to run separately and it is bridged somehow (God, not over the network)?
Now if you ask me, even stored procedures in general become more and more evil.
And in our age of $50 2Ghz CPUs and Gigabit ehternet the performance is no longer an issue.
To me, a database is a collection of tables and indexes with referencial integrity, failover and redundancy. It should do just one thing and do it well. Attempts to add features like that seem to be just a marketing thing by their new commercial overlords.
Or Python? (Score:2, Insightful)
Re:Now how about. (Score:2, Insightful)
There needs to be someway of doing online back ups of MySQL with out spending money.
Re:That's great (Score:3, Insightful)
Just FYI - MySQL still doesn't support stored procedures, let alone Java inside stored procedures. Seems like MySQL is trying to run before it's gotten the walking thing down yet.
Re:Sounds like... (Score:5, Insightful)
limiting the # of rows of output is different between oracle, sybase and postresql/mysql.
None of them even have remotely the same stored proc language. Of course, everyone may embed a different language, but java seems to be a more common one.
Now when you go from sybase to oracle, you don't have to worry so much about the stored procedure code, since it'd all be in java anyway.. riight?
It would be if it were true. (Score:1, Insightful)
Re:Keep this out. (Score:3, Insightful)
But it doesn't go away.
I have noticed that there are several technologies that are held in high regard outside of the Linux/Free Software that are despised within it.
One is Object Oriented programming. By extension, C++, Java, and UML also fit into this category.
I wonder how many folks who bash these things have ever actually bothered to learn them?
It is easier to say that XYZ is "bloated and ugly" than to say "I never learned these things so I can't say how useful they are."
I also see a lot of "Anyone that does not agree with me is a stupid, clueless, MCSE."
Name calling is a sign of weak arguments.
The article is about Java running on the server, behind the scenes. It doesn't "look" like anything.
I believe server side java is the most common usage of Java. Portability is less of an issue because you control the server environment.
You can support non-Unix users and still use Unix/Linux for your server.
Not my first priority (Score:3, Insightful)
Java is not my first choice in languages to support in a database language. PL would have at least been more adaptable.
Unfortunately with the Enterprise Popularity of Java, thanks to a strong Marketing Campaign by Sun Microsystems, MySQL is following the Corporate line of supporting Java regardless. This is a fine example of what may be a mis-direction of the MySQL developers being pushed into a Support the Corporate Enterprise stuff rather then doing good code on a good platform.
Re:Sounds like... (Score:2, Insightful)
Re:Not my first priority (Score:3, Insightful)
Re:Now how about. (Score:1, Insightful)
except that for the skill requirements (Score:3, Insightful)
Does the LAMP crowd write code in java? nope.
Do the DBAs write code in java? nope.
Does the java crowd use mysql? nope (if you're going to the cost of developing apps in java, it makes more sense to use postgresql if not oracle, db2, etc).
In java you can abstract the data persistence thru a variety of encasulation techniques. All of which creates such a mess than everyone's scrambling these days to figure out how to simplify it. Sounds like a mess to introduce deeper into the database.
And portability? Do you really think that java functions created for mysql will port *seamlessly* to postgresql, db2, or oracle? No way. And if they don't - why don't you simply write the functions in a tiny, simplistic language that everyone can use easily?
Re:PHP has this for over a year (Score:3, Insightful)
Cool. Very cool. But those execution times are pretty bad. You certainly would want to plan carefully how you used this.
--Richard
Re:Old hat (Score:4, Insightful)
SO? Oracle has lots of features that MySQL lacks. The point of the post isn't that this is some wonderful new feature never before seen in the world, only that it's new to MySQL.
Oh, and one of the fabulous features that Oracle has over MySQL is the price. I mean, who wouldn't prefer to spend many thousands of dollars? This is obviously another area where OSS needs to start playing catch-up.