Building Distributed
Applications
Using the Progress AppServer


Schema Triggers

Schema trigger code defined in the database is executed by database clients. Any database access by an Application Server process that invokes database trigger code causes the Application Server process to run such code. This is because the AppServer application acts as a client to the database.

There is no functional difference between how schema triggers run in an AppServer session and how they run in a 4GL client session. However, trigger code executed by an Application Server process:

Invoking schema triggers on a client application raises a basic security issue. Code in the Application Server process is protected because of encapsulation; code on your client application is not protected.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095