Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 3 of 3 total |
Collecting Schema Information |
Wed, Aug 4 2010 5:14 AM | Permanent Link |
Ivan | Hi All,
I would like to be able to obtain Schema information from ElevateDB on a particular Database. I want to use this information to validate import data and to ensure that the number of columns in the import (say CSV) matches the number and datatype of fields in a selected Table. I know you can use ADO.NET to obtain schema information, just wondering if there is another way in ElevateDB such as using the Engine Namespace ? Cheers, Kind Regards, Ivan |
Wed, Aug 4 2010 5:42 AM | Permanent Link |
Franco Fustini | Ivan wrote:
Hi All, I would like to be able to obtain Schema information from ElevateDB on a particular Database. I want to use this information to validate import data and to ensure that the number of columns in the import (say CSV) matches the number and datatype of fields in a selected Table. I know you can use ADO.NET to obtain schema information, just wondering if there is another way in ElevateDB such as using the Engine Namespace ? Cheers, Kind Regards, Ivan 'SELECT * FROM INFORMATION.TABLES' or from whatever other kind of info is contained in Information Schema: From the Help: Information Schema The tables that make up the Information schema for each database are as follows: Tables Table TablePrivileges Table TableColumns Table TemporaryTables Table Constraints Table ConstraintColumns Table Indexes Table IndexColumns Table Triggers Table TriggerColumns Table Views Table ViewPrivileges Table ViewColumns Table TemporaryViews Table Procedures Table ProcedurePrivileges Table ProcedureParams Table Functions Table FunctionPrivileges Table FunctionParams Table The metadata that these tables are based upon is stored in the catalog file (EDBDatabase.EDBCat, by default) located in the database folder where the database was created. See the CREATE DATABASE statement for more information on creating a database. SQL 2003 Standard Deviations -------------------------------------------------------------------------------- The following areas are where ElevateDB deviates from the SQL 2003 standard: Deviation Details Extended Objects Indexes are an ElevateDB extension, and these objects are not defined in the SQL 2003 standard. |
Wed, Aug 4 2010 7:18 AM | Permanent Link |
Ivan | Franco Fustini wrote:
Ivan wrote: Hi All, I would like to be able to obtain Schema information from ElevateDB on a particular Database. I want to use this information to validate import data and to ensure that the number of columns in the import (say CSV) matches the number and datatype of fields in a selected Table. I know you can use ADO.NET to obtain schema information, just wondering if there is another way in ElevateDB such as using the Engine Namespace ? Cheers, Kind Regards, Ivan 'SELECT * FROM INFORMATION.TABLES' or from whatever other kind of info is contained in Information Schema: From the Help: Information Schema The tables that make up the Information schema for each database are as follows: Tables Table TablePrivileges Table TableColumns Table TemporaryTables Table Constraints Table ConstraintColumns Table Indexes Table IndexColumns Table Triggers Table TriggerColumns Table Views Table ViewPrivileges Table ViewColumns Table TemporaryViews Table Procedures Table ProcedurePrivileges Table ProcedureParams Table Functions Table FunctionPrivileges Table FunctionParams Table The metadata that these tables are based upon is stored in the catalog file (EDBDatabase.EDBCat, by default) located in the database folder where the database was created. See the CREATE DATABASE statement for more information on creating a database. SQL 2003 Standard Deviations -------------------------------------------------------------------------------- The following areas are where ElevateDB deviates from the SQL 2003 standard: Deviation Details Extended Objects Indexes are an ElevateDB extension, and these objects are not defined in the SQL 2003 standard. Thanks very much for your reply, and I had forgotten about this information, but remember it now that you have reminded me. Thanks for that, I will go and look at using these tables now. Cheers, and thanks for a quick reply. kind Regards, Ivan |
This web page was last updated on Saturday, April 27, 2024 at 08:52 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |