Building Distributed
Applications
Using the Progress AppServer
Minimizing the Effects of Schema Changes
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 your 4GL client application to be independent of database schema, you can use the AppServer to minimize the effects of schema changes by masking the changes from the client application.
The following list identifies specific techniques you should use to shield these schema changes from affecting client applications:
- Set up database access so that it is accomplished entirely through Application Server processes (the client is not connected to the database and all records are transferred from the Application Server process through temporary table parameters).
- Avoid using LIKE syntax for temporary tables and variables in client application code and in procedure parameters for remote procedures.
- Application Server process code must map data based on the new schema to the existing procedure parameters for the remote procedure.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |