Kbase P170613: 4GL/SQL: How to maintain referential integrity when developing an SQL interface against an OpenEdge
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
03/08/2010 |
|
Status: Unverified
GOAL:
4GL/SQL: How to maintain referential integrity when developing an SQL interface against an OpenEdge database that already has an OpenEdge 4GL interface?
GOAL:
Do you have any recommendations or "best practice" documents on how to manage a database accessed by both SQL clients and by OpenEdge 4GL/ABL clients?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
FIX:
Progress does not offer any formal recommendations or a 'best practices' list on this subject. The OpenEdge (4GL/ABL) database referential integrity is maintained using 4GL/ABL (OpenEdge) database event triggers. To create an OpenEdge JDBC SQL application comparable to an existing OpenEdge 4GL/ABL application, you need to create a parallel set of Java database event triggers that is functionally equivalent to the existing OpenEdge 4GL database event triggers. This will maintain the OpenEdge database referential integrity regardless of whether it is accessed by a 4GL/ABL client or an SQL client.