• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

J2EE & PL/SQL  RSS feed

 
Ranch Hand
Posts: 1061
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I just learn the PL/SQL syntax, because I saw so many Job-Offerings with the required skill combination of J2EE and PL/SQL. But i can't make a picture how it's fitting together.
My question:

What are typical environments for such a setting?
- e.g. would i have to expect a migration project?
- or is it common, that parts of the business logic reside in these DB-scripts and there is a interface to the J2EE side?

Thanks and Sorry, if this is not the right forum
cb
 
Ranch Hand
Posts: 333
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
PL/SQL is the stored procedure language for Oracle databases (maybe somebody else has adopted the syntax as well, but I don't know that). Other databases use other stored procedure languages (some even use Java, including Oracle as an alternative language).

A J2SE (or J2EE) program can invoke a database stored procedure (of any language) using JDBC's CallableStatement.
 
author
Bartender
Posts: 4096
21
Eclipse IDE Flex Google Web Toolkit
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Don't worry Chris, this is the forum for that (although there is an Oracle forum for Oracle-specific questions if you want to job working with Oracle).

The picture is cloudy at best. The original intent was that complex database transactions/procedures would be put in a stored procedure and the application would make simplistic calls to the database. Some systems have done an excellent job utilitizing this especially in the cases of procedures would be highly expensive if handled by business logic.

These days though, especially with J2EE and object relational mappings, such systems are not that common. At some point there became a need for application servers to have more control over their data, coupled with the fact that stored procedures are *extremely* non-portable (trying rewriting 1000+ stored procedures to switch databases...) and they are becomming a rare sight.

In fact, the only time I see them used anymore in business logic is to perform read-only queries that would be too costly (either network bandwidth or processing power) to perform by the application server.
 
Chris Baron
Ranch Hand
Posts: 1061
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks a lot for the orientation.
cb
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!