v5:dictionary:dictionary_index
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
dictionary:data_dictionary [2015/10/26 03:48] – [XML Driven Functions] mnewnham | v5:dictionary:dictionary_index [2021/01/05 04:06] – ↷ Links adapted because of a move operation 54.36.148.153 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | <WRAP right box> | ||
+ | [[v5: | ||
+ | </ | ||
====== The Data Dictionary ====== | ====== The Data Dictionary ====== | ||
===== Introduction ===== | ===== Introduction ===== | ||
Line 4: | Line 7: | ||
===== Portable Data Types ===== | ===== Portable Data Types ===== | ||
- | ADOdb provides a cross-platform method of identifying the data type of a field. These values can be used as a replacement in code that relies on the data type of field to produce a result. Each database driver contains a cross-reference table of datatypes that can accessed using the [[dictionary: | + | ADOdb provides a cross-platform method of identifying the data type of a field. These values can be used as a replacement in code that relies on the data type of field to produce a result. Each database driver contains a cross-reference table of datatypes that can accessed using the [[v5:dictionary: |
- | ==== Summary Of Types ==== | + | ==== Summary Of Standard |
- | ^ Type ^ Represents Field Types ^ When Using addColumnSql | + | ^ Type ^ Represents Field Types ^ When Using addColumnSql |
- | | C | character fields that should be shown in a <input type=" | + | | C | character fields that should be shown in a <input type=" |
- | | X | TeXt, large text fields that should be shown in a < | + | | C2 | Like a C field, but where possible a field that can hold multi-byte (unicode) data is created |
- | | B | Blobs, or Binary Large Objects. Typically images. | + | | X | TeXt, large text or CLOB fields that should be shown in a < |
- | | D | Date field | | + | | X2 | Like an X field, but where possible creates a field that can hold multi-byte (unicode) data is created |
- | | T | Timestamp field | + | | XL | On systems that support it, creates a large clob field (32K). This may require additional database configuration. If the database does not support it, a standard clob field is created. |
- | | L | Logical field (boolean or bit-field). Some databases emulate logicals using I2 fields | + | | B | Blobs, or Binary Large Objects. Typically images. |
- | | I | Integer field, This may be broken down further into I2,I4 or I8 types | + | | D | Date (sometimes DateTime) |
- | | N | Numeric field. Includes autoincrement, | + | | T | Timestamp field |
- | | R | Serial field. Includes serial, autoincrement integers. This works for selected databases. Some databases do not signify if a field is auto-increment | + | | L | Logical field (boolean or bit-field). Some databases emulate logicals using I2 fields |
+ | | I | Integer field, This may be broken down further into I2,I4 or I8 types to represent small, | ||
+ | | N | Numeric field. Includes autoincrement, | ||
+ | | R | Serial field. Includes serial, autoincrement integers. This works for selected databases. Some databases do not signify if a field is auto-increment | ||
==== Using Data Types For Non-Portable Applications ==== | ==== Using Data Types For Non-Portable Applications ==== | ||
- | There are benefits to using ADOdb data types even when writing an application that is not designed to be portable. The '' | + | There are benefits to using ADOdb data types even when writing an application that is not designed to be portable. The '' |
^Data Type^Description^ | ^Data Type^Description^ | ||
Line 26: | Line 32: | ||
===== The Meta Functions ===== | ===== The Meta Functions ===== | ||
- | Metadata functions convert database specific table, column and index queries into a standardized cross-database format. As of ADOdb version 6.0, the casing of keys and values returned by the metaFunctions can be controlled by [[dictionary: | + | Metadata functions convert database specific table, column and index queries into a standardized cross-database format. |
- | | [[dictionary: | + | | [[v5:dictionary:actualtype|actualType()]] |
- | | [[dictionary: | + | | [[v5: |
- | | [[dictionary: | + | | [[v5: |
- | | [[dictionary: | + | | [[v5:dictionary:metacolumns|metaColumns()]] |
- | | [[dictionary: | + | | [[v5:dictionary:metacolumnnames|metaColumnNames()]] |
- | | [[dictionary: | + | | [[v5:dictionary: |
- | | [[dictionary: | + | | [[v5:dictionary:metaforeignkeys|metaForeignKeys()]] |
- | | [[dictionary: | + | | [[v5:dictionary: |
- | | [[dictionary: | + | | [[v5:dictionary:metaprimarykeys|metaPrimaryKeys()]] |
- | | [[dictionary: | + | | [[v5:dictionary:metaprocedures|metaProcedures()]] |
- | | [[dictionary: | + | | [[v5:dictionary:metatables|metaTables()]] |
- | | [[dictionary: | + | | [[v5:dictionary: |
+ | | [[v5:dictionary: | ||
+ | | [[v5: | ||
+ | | [[v5: | ||
+ | | [[v5:dictionary: | ||
===== Schema Management ===== | ===== Schema Management ===== | ||
<WRAP info> | <WRAP info> | ||
Line 45: | Line 55: | ||
</ | </ | ||
==== Executing prepared code to update the schema ==== | ==== Executing prepared code to update the schema ==== | ||
- | Each of the methods below return an array of data, which should be executed using the [[dictionary: | + | Each of the methods below return an array of data, which should be executed using the [[v5:dictionary: |
+ | |||
+ | ==== Creating A Database ==== | ||
+ | | [[v5: | ||
==== Managing Tables ==== | ==== Managing Tables ==== | ||
- | | [[dictionary: | + | | [[v5:dictionary: |
- | | [[dictionary: | + | | [[v5:dictionary: |
- | | [[dictionary: | + | | [[v5:dictionary: |
- | | [[dictionary: | + | | [[v5:dictionary: |
==== Managing Columns ==== | ==== Managing Columns ==== | ||
- | | [[dictionary: | + | | [[v5:dictionary: |
- | | [[dictionary: | + | | [[v5:dictionary: |
- | | [[dictionary: | + | | [[v5:dictionary: |
- | | [[dictionary: | + | | [[v5:dictionary: |
==== Managing Indexes ==== | ==== Managing Indexes ==== | ||
- | | [[dictionary: | + | | [[v5:dictionary: |
- | | [[dictionary: | + | | [[v5:dictionary: |
+ | ==== Managing Database Column Comments ==== | ||
+ | |[[v5: | ||
+ | |[[v5: | ||
===== XML Driven Functions ===== | ===== XML Driven Functions ===== | ||
- | [[dictionary: | + | See the section on [[v5:dictionary:xmlschema|ADOdb-xmlschema]] |
v5/dictionary/dictionary_index.txt · Last modified: 2023/06/04 11:41 by dregad