Difference between revisions of "SQL Database Events"
Yvonnemilne (Talk | contribs) |
Yvonnemilne (Talk | contribs) |
||
| Line 16: | Line 16: | ||
==Description== | ==Description== | ||
Database events are triggered by certain database operations. They can have code associated with them that is run automatically when the event occurs. | Database events are triggered by certain database operations. They can have code associated with them that is run automatically when the event occurs. | ||
| − | |||
| Line 27: | Line 26: | ||
|- | |- | ||
|} | |} | ||
| + | |||
Databases in Recital are implemented as directories containing files that correspond to the tables and associated files in the database. Operating System file protection can be applied individually to the files for added security. The directories are sub-directories of the Recital data directory. The environment variable / symbol DB_DATADIR points to the current Recital data directory and can be queried using the GETENV() function. Files from other directories can be added to the database using the ADD TABLE command or via the database catalog and SET AUTOCATALOG functionality. | Databases in Recital are implemented as directories containing files that correspond to the tables and associated files in the database. Operating System file protection can be applied individually to the files for added security. The directories are sub-directories of the Recital data directory. The environment variable / symbol DB_DATADIR points to the current Recital data directory and can be queried using the GETENV() function. Files from other directories can be added to the database using the ADD TABLE command or via the database catalog and SET AUTOCATALOG functionality. | ||
Programs associated with database events should reside in the DB_DATADIR sub-directory for the relevant database. | Programs associated with database events should reside in the DB_DATADIR sub-directory for the relevant database. | ||
| − | |||
Revision as of 14:26, 19 March 2009
DATABASE EVENTS
Class
Databases
Purpose
Database events are triggered by certain database operations
See Also
ADATABASES(), ALTER TABLE, ADD TABLE, ALTER INDEX, BACKUP DATABASE, CLOSE DATABASES, CLOSE TABLES, COMPILE DATABASE, CREATE DATABASE, CREATE TABLE, CREATE INDEX, CREATE VIEW, DATABASE(), DB_DATADIR, DB_MAXWKA, DBUSED(), DISPLAY DATABASE, DISPLAY INDEXES, DISPLAY TABLES, DROP DATABASE, DROP INDEX, DROP TABLE, GETENV(), LIST DATABASE, LIST INDEXES, LIST TABLES, OPEN DATABASE, PACK DATABASE, REBUILD DATABASE, REINDEX DATABASE, RESTORE DATABASE, SET AUTOCATALOG, SET EXCLUSIVE, USE
Description
Database events are triggered by certain database operations. They can have code associated with them that is run automatically when the event occurs.
| Event | Description |
|---|---|
| DBC_CLOSEDATA | Occurs when a database closes |
| DBC_OPENDATA | Occurs when a database is opened |
Databases in Recital are implemented as directories containing files that correspond to the tables and associated files in the database. Operating System file protection can be applied individually to the files for added security. The directories are sub-directories of the Recital data directory. The environment variable / symbol DB_DATADIR points to the current Recital data directory and can be queried using the GETENV() function. Files from other directories can be added to the database using the ADD TABLE command or via the database catalog and SET AUTOCATALOG functionality.
Programs associated with database events should reside in the DB_DATADIR sub-directory for the relevant database.
Products
Recital Database Server, Recital Mirage Server, Recital Terminal Developer
