Kbase P114758: What are the effects of database changes in 4GL if SQL tables are created within the PUB schema?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
What are the effects of database changes in 4GL if SQL tables are created within the PUB schema?
GOAL:
Can a SQL table be accessed from 4GL?
GOAL:
How does SQL tables impact the CRC of 4GL r-code?
GOAL:
How is it possible to create a SQL table that can be accessed from the ABL?
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
FIX:
Basically SQL tables created in the PUB schema will behave like regular 4GL tables from the 4GL point of view. They can be accessed from 4GL using regular database statements, as long as the data types are compatible with 4GL, as stated in the Progress documentation. Also, the r-code will need recompilation when the SQL table definition is changed, i.e. table CRC checks are affected as stated in solution P8326, What dictionary changes force recompiling: Time Stamp and CRC?.
However the following items need to be taken into consideration:
- SQL triggers and table referential constraints are not checked when the table is used from 4GL.
- The SQL engine creates automatically indexes to support the PRIMARY KEY and UNIQUE constraints. These indexes have automatically generated names prefixed with SYS_. These names are different across databases, even if the data definition is the same.