v5:dictionary:dictionary_index
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
v5:dictionary:dictionary_index [2016/01/13 04:00] – ↷ Page name changed from v5:dictionary:index to v5:dictionary:dictionary_index mnewnham | v5:dictionary:dictionary_index [2024/12/18 10:19] (current) – [Introduction] dregad | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | <WRAP right box> | ||
+ | [[v5: | ||
+ | </ | ||
====== The Data Dictionary ====== | ====== The Data Dictionary ====== | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | The Data Dictionary provides a series of functions | + | The Data Dictionary provides a series of **' |
===== 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 [[v5: | 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: | ||
- | ==== 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 or CLOB 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 (sometimes DateTime) 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 to represent small, | + | | D | Date (sometimes DateTime) field |
- | | 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 '' | ||
Line 29: | Line 35: | ||
| [[v5: | | [[v5: | ||
+ | | [[v5: | ||
+ | | [[v5: | ||
| [[v5: | | [[v5: | ||
| [[v5: | | [[v5: | ||
Line 39: | Line 47: | ||
| [[v5: | | [[v5: | ||
| [[v5: | | [[v5: | ||
- | | [[v5: | + | | [[v5: |
+ | | [[v5: | ||
+ | | [[v5: | ||
===== Schema Management ===== | ===== Schema Management ===== | ||
<WRAP info> | <WRAP info> | ||
- | The userid | + | The user id used when establishing a database connection may need specific privileges beyond normal INSERT, DELETE, UPDATE, SELECT in order to manage a schema in a database. Those privileges vary from one DBMS to another. |
</ | </ | ||
==== Executing prepared code to update the schema ==== | ==== Executing prepared code to update the schema ==== | ||
- | Each of the methods below return | + | |
+ | Each of the methods below returns | ||
==== Creating A Database ==== | ==== Creating A Database ==== | ||
- | |[[v5: | + | | [[v5: |
==== Managing Tables ==== | ==== Managing Tables ==== |
v5/dictionary/dictionary_index.1452654035.txt.gz · Last modified: 2017/04/21 11:28 (external edit)