v5:database:ibm_db2
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
database:ibm_db2 [2015/12/03 20:29] – [Driver Specific Options] mnewnham | v5:database:ibm_db2 [2016/01/13 02:06] – ↷ Links adapted because of a move operation mnewnham | ||
---|---|---|---|
Line 11: | Line 11: | ||
^ADOdb V6|Yes| | ^ADOdb V6|Yes| | ||
== Alternative Drivers == | == Alternative Drivers == | ||
- | [[database: | + | [[v5:database: |
</ | </ | ||
===== Description ===== | ===== Description ===== | ||
- | This driver provides a connection to IBM DB2 Databases, using the IBM Data Client. | + | This driver provides a connection to IBM DB2 Databases, using the IBM Data Client. This driver replaces the original [[v5: |
- | + | ---------------------------------- | |
==== uCaseTables ==== | ==== uCaseTables ==== | ||
<WRAP right box> | <WRAP right box> | ||
Line 26: | Line 25: | ||
</ | </ | ||
- | This variable sets the keys in [[dictionary: | + | This variable sets the keys in [[v5:dictionary:metacolumns]],[[v5:dictionary:metaprimarykeys]] and [[v5:dictionary:metaforeignkeys]] to upper-case when retrieved. The default is true. |
<code php> | <code php> | ||
Line 72: | Line 71: | ||
</ | </ | ||
- | This driver re-maps ibm :0 bind variables to oracle compatible ? variables. Use this driver to enhance compatiblity between [[database:Oracle]] and DB2 drivers | + | This driver re-maps ibm :0 bind variables to oracle compatible ? variables. Use this driver to enhance compatiblity between [[v5:database:oracle]] and DB2 drivers |
------------------------------------------------- | ------------------------------------------------- | ||
Line 121: | Line 120: | ||
Any table name containing special characters will need to be quoted in all queries. | Any table name containing special characters will need to be quoted in all queries. | ||
- | ==== Using metaCasing with DB2 ==== | ||
- | When using DB2, it is important to remember that when using [[dictionary: | ||
- | |||
- | Generally, development standards mean that table names in a database are created to a casing standard, for example, all upper-case or lower-case table and column names. In that case, metaCasing will work the same as in other databases, e.g. | ||
- | <code php> | ||
- | /* | ||
- | * Connection to DB2 smple database, accessing a table called ACT | ||
- | * Set the casing to lower case | ||
- | */ | ||
- | $db-> | ||
- | $cols = $db-> | ||
- | print_r($cols); | ||
- | /* | ||
- | * Prints | ||
- | Array( | ||
- | [0] => actno, | ||
- | [1] => actname, | ||
- | [2] => actdesc | ||
- | ) | ||
- | */ | ||
- | |||
- | </ | ||
- | ----------------- | ||
- | <WRAP right info 300px> | ||
- | These rules also apply to column naming | ||
- | </ | ||
- | ===== The Impact Of METACASE_NATIVE ===== | ||
- | Setting the metaCasing option to '' | ||
- | ==== Creating Tables ==== | ||
- | Consider the following case-sensitive table name: '' | ||
- | |||
- | ^MetaCase^Created As^SQL Retrieval^Presentation in MetaFunctions^ | ||
- | |METACASE_UPPER|ACCOUNTTABLE|SELECT FROM ACCOUNTTABLE, | ||
- | |METACASE_LOWER|ACCOUNTTABLE|SELECT FROM ACCOUNTTABLE, | ||
- | |METACASE_NATIVE|accountTable|SELECT FROM " | ||
- | |||
- | As shown, once a table is created in non-upper case when the metaCasing value is '' | ||
{{tag> | {{tag> |
v5/database/ibm_db2.txt · Last modified: 2024/05/25 04:30 by mnewnham