I want to write an experimental JDBC client application with OE as the database. One of the basic requirements is that the JDBC client be able to invoke Stored Procedures defined in the OpenEdge database. The eventual goal is to write a full-scale application using Spring and Hibernate for the back end with an Angular front-end.
Can someone point me in the right direction that helps me understand how to define and use Stored Procedures for an OE database
A simple example for:
Defining such a Stored Procedure
How a JDBC client would utilize such a Stored Procedure
I can't really imagine why would anyone use the OE (R)DBMS without the 4GL so just for storage and not business logic since there are plenty of good SQL database engines out there either open source or less expensive than OE... if there is some existing business logic, or the plan is to write that in 4GL, then our JDBC driver make it very easy to expose that as 'stored procedures' - http://acorn.ro/products/abl-jdbc/
Thanks @makhtar for the very helpful URLs.
The need is to eventually migrate from Progress RDBMS with the first phase focusing on converting the application logic from Progress 4GL to Java/JDBC. Where SQL92 Triggers come into the picture is trying to answer to the needs of real-time invocation of logic based on database events that are affected by the Java/JDBC logic. This need stems from the fact that 4GL Triggers are not invoked from application logic that is not written in Progress 4GL.
[mention:d768d2089b264b89b29e49c0617a193b:e9ed411860ed4f2ba0265705b8793d05], Since SQL Triggers are also considered a case of Stored Procedure in the world of Progress SQL, I am afraid I conflated the two in my OP.
In fact, the main objective is to use SQL Triggers for database events (INSERT, UPDATE, DELETE...) via JDBC clients. The use case is a parallel to where you would use 4GL database triggers for database events via a 4GL client.
Thanks for pointing me to your JDBC driver. Since one of the core objectives is to get away from Progress licenses and move towards an Open Source strategy, this cannot go in the direction you are suggesting, since that involves maintaining the AppServer license. We will, however, be looking to get the DataDirect JDBC driver.
> On May 16, 2019, at 9:36 AM, v205 wrote:
> We will, however, be looking to get the DataDirect JDBC driver.
the JDBC driver that comes with the OpenEdge RDBMS /is/ the DataDirect driver. if you dont have it already you can download it from ESD at no charge.
@Gus, thank you for pointing that out. I was not sure if they are the same exact driver. Much appreciated.