 |  LoginProducts  SalesSupportDownloadsAbout |
| Home » Technical Support » ElevateDB Technical Support » Product Manuals » ElevateDB Version 2 SQL Manual » System Information » SchemaObjects Table |
SchemaObjects TableStructure
Description
This table contains all objects in an ElevateDB database in their dependency-sensitive creation order. This table can be used to generate a script for creating/dropping all objects in a database in a manner that will not generate any dependency errors.
In order to generate a proper CREATE script, simply navigate this table from the first row to the last row, using the CreateSQL column for the CREATE SQL statements for each object. After this initial pass, navigate this table again from the first row to the last row, using the PostCreateSQL column for any remaining ALTER SQL statements that may exist for dealing with objects that contain mutual depdendencies between each other, such as the case with two tables that have foreign keys that refer to the other table.
If you wish to include populating tables with existing rows in your CREATE script, you should do so before including any PostCreateSQL statements that may exist.
In order to generate a proper DROP script, simply navigate this table in reverse order from the last row to the first row, using the PreDropSQL column for any ALTER SQL statements that may exist for dealing with objects that contain mutual dependencies between each other, and need to have these dependencies removed before the objects can be dropped. After this initial pass, navigate this table again in reverse order from the last row to the first row, using the DropSQL column for the DROP SQL statements for each object.
Sub-objects such as indexes and triggers for tables are not specified in this table. Because such objects are not dependency-sensitive, they can be created according to the order that they appear in in their corresponding system information table such as the Indexes and Triggers tables. Simply query these tables for a given parent table name to retrieve the list of sub-objects.
The ParentType and Type column values are as follows:
Related DDL Statements
CREATE TABLE "SchemaObjects"
(
"ParentName" VARCHAR(40) COLLATE "ANSI_CI",
"ParentType" VARCHAR(15) COLLATE "ANSI_CI",
"Name" VARCHAR(40) COLLATE "ANSI_CI",
"Type" VARCHAR(15) COLLATE "ANSI_CI",
"CreateSQL" CLOB COLLATE "ANSI_CI",
"PostCreateSQL" CLOB COLLATE "ANSI_CI",
"PreDropSQL" CLOB COLLATE "ANSI_CI",
"DropSQL" CLOB COLLATE "ANSI_CI"
)
CREATE INDEX "ParentName" ON "SchemaObjects"
("ParentName")
CREATE INDEX "ParentType" ON "SchemaObjects"
("ParentType")
CREATE INDEX "Name" ON "SchemaObjects"
("Name")
CREATE INDEX "Type" ON "SchemaObjects"
("Type")Description
This table contains all objects in an ElevateDB database in their dependency-sensitive creation order. This table can be used to generate a script for creating/dropping all objects in a database in a manner that will not generate any dependency errors.
In order to generate a proper CREATE script, simply navigate this table from the first row to the last row, using the CreateSQL column for the CREATE SQL statements for each object. After this initial pass, navigate this table again from the first row to the last row, using the PostCreateSQL column for any remaining ALTER SQL statements that may exist for dealing with objects that contain mutual depdendencies between each other, such as the case with two tables that have foreign keys that refer to the other table.
If you wish to include populating tables with existing rows in your CREATE script, you should do so before including any PostCreateSQL statements that may exist.In order to generate a proper DROP script, simply navigate this table in reverse order from the last row to the first row, using the PreDropSQL column for any ALTER SQL statements that may exist for dealing with objects that contain mutual dependencies between each other, and need to have these dependencies removed before the objects can be dropped. After this initial pass, navigate this table again in reverse order from the last row to the first row, using the DropSQL column for the DROP SQL statements for each object.
Sub-objects such as indexes and triggers for tables are not specified in this table. Because such objects are not dependency-sensitive, they can be created according to the order that they appear in in their corresponding system information table such as the Indexes and Triggers tables. Simply query these tables for a given parent table name to retrieve the list of sub-objects.The ParentType and Type column values are as follows:
| Type | Description |
| Table | The object is a table |
| View | The object is a view |
| Procedure | The object is a procedure |
| Function | The object is a function |
Related DDL Statements
| Statement | Description |
| CREATE TABLE | Creates a new table |
| CREATE TRIGGER | Creates a new trigger |
| CREATE INDEX | Creates a new index |
| CREATE VIEW | Creates a new view |
| CREATE PROCEDURE | Creates a new procedure |
| CREATE FUNCTION | Creates a new function |
| DROP TABLE | Drops an existing table |
| DROP TRIGGER | Drops an existing trigger |
| DROP INDEX | Drops an existing index |
| DROP VIEW | Drops an existing view |
| DROP PROCEDURE | Drops an existing procedure |
| DROP FUNCTION | Drops an existing function |
More Support Options
This web page was last updated on Friday, January 31, 2025 at 08:42 AM | Privacy PolicySite Map © 2025 Elevate Software, Inc. All Rights Reserved Questions or comments ?  E-mail us at info@elevatesoft.com |
