Answered What is the significance of "override procedure" when we define a schema trigger.?

[Kevin Tony]

1. Why we use override procedure while defining a schema trigger.

eg:- TABLE-TRIGGER "create" override procedure "CUSTOMER.TRG" CRC "?"

2. Also why we use "area" while creating table or index. Is it mandatory to specify the area.
eg:- Area "Data Area"

3. What CRC "?" does ?

 

[Kevin Tony]

1. Override procedure - let the trigger procedure be overridable by a trigger local to a specific application procedure.

 

[Rob Fitzpatrick]

Also why we use "area" while creating table or index. Is it mandatory to specify the area.
eg:- Area "Data Area"

If you don't explicitly specify the storage area for a new table or index, it is placed in the schema area. The schema area is a Type I storage area that should only contain the database schema. It should not contain any of your application objects.

Proper storage area planning is an important foundation for database scalability, performance, and maintenance. I suggest you download the PDF documentation set for your version of Progress and read the Database Essentials manual, specifically chapters 3 (OpenEdge RDBMS) and 4 (Administrative Planning). It discusses what storage areas are and gives some basic guidelines for configuring them. If you are tasked with making schema changes on a database, you need to understand this.

 

[Kevin Tony]

Thanks alot Rob.

 

[Kevin Tony]

If anyone wants to read regarding the above topic -
https://community.progress.com/cfs-...omponents-files/00-00-00-00-15/6562.gsdbe.pdf