Kbase P107836: How to minimize the effects of Schema Changes when designing an AppServer Client application?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/08/2005 |
|
Status: Unverified
GOAL:
How to minimize the effects of Schema Changes when designing an AppServer Client application?
GOAL:
How to exchange TEMP-TABLEs between the client and the AppServer without having to connect the client to the database?
FIX:
In the traditional client/server model where all 4GL clients are connected to a database, database schema changes can invalidate r-code run by the client. In contrast, by designing the 4GL client application to be independent of database schema, the AppServer may be used to to minimize the effects of schema changes by masking the changes from the client application.
The following are some techniques that may be used to shield these schema changes from affecting client applications:
1. Set up database access so that it is accomplished entirely through Application Server processes.
2. Avoid using LIKE syntax for temporary tables and variables in the client application code and in procedure parameters for remote procedures.