I agress with most of what you've said. >> Stored procedures do not ensure anything other than a lack of portability.
I do know that this is always brought up, but it is irrelevant in most cases. Enterprises do not switch out their database vendors nearly often enough for this to be a remote care. If you are developing components for resale, that's another story. But if you are building code for a company that serves an explicit need, portability should not be on your top ten priority list. There are far more important matters to address first. Not to get off topic, but I don't see a great benefit to having developers learn a sql language that is not true sql. I contend that the odds are greater that your object layer has a much better chance of moving from java to .net than your db moving from sql server to oracle. Considering this, just learn SQL. It's not hard. It's the single most transitive skill for a developer to have. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927975#3927975 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3927975 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
