This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
integration:rdbms:odbc:databases [2011/04/06 17:43] 127.0.0.1 external edit |
integration:rdbms:odbc:databases [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 21: | Line 21: | ||
| ==== Databases ==== | ==== Databases ==== | ||
| - | The [[dev:sql:statements:create_database:home|CREATE DATABASE]] statement is used to declare an ODBC database within an Omnidex Environment File. This statement can either be issued directly, or it can be extracted from ODBC using the EXTRACT statement as discussed in the previous section. | + | The [[dev:sql:statements:create_database:home|CREATE DATABASE]] statement is used to declare a database within an Omnidex Environment File to be accessed through ODBC. This statement can either be issued directly, or it can be extracted from the database using the EXTRACT statement as discussed in the previous section. |
| - | The CREATE DATABASE statement must include the DSN or File DSN that identifies the ODBC database, as well as the ODBC user and password. Note that the datatype type is ODBC, with a subtype of MYSQL, reflecting that ODBC is the primary method of accessing a ODBC database. | + | The CREATE DATABASE statement must include the datasource that connects to the underlying database, as well as a user and password. It is recommended to use a System DSN, rather than a User DSN, so that the DSN will be accessible across all users and from the Omnidex Network Services. |
| <code> | <code> | ||
| create database "SIMPLE" | create database "SIMPLE" | ||
| type odbc | type odbc | ||
| - | subtype mysql | ||
| dsn "simple" | dsn "simple" | ||
| user "simple" | user "simple" | ||
| Line 41: | Line 40: | ||
| * Administrators can register a user and password in the ODBC datasource. | * Administrators can register a user and password in the ODBC datasource. | ||
| - | * Administrators can register a user and password in the Omnidex Environment File. This user and password will always be used to access the ODBC database, and no users and passwords will be needed from the application. | + | * Administrators can register a user and password in the Omnidex Environment File. This user and password will always be used to access the database, and no users and passwords will be needed from the application. |
| * The application can pass a user and password in the [[dev:connections:home|Omnidex Connection String]]. This user and password is then passed directly to ODBC to access the database. | * The application can pass a user and password in the [[dev:connections:home|Omnidex Connection String]]. This user and password is then passed directly to ODBC to access the database. | ||
| - | One of these approaches must be used to allow connections to the ODBC database. Administrators should insure that the user and password provides access to all of the database objects referenced in the Omnidex Environment Files. | + | One of these approaches must be used to allow connections to the database through ODBC. Administrators should insure that the user and password provides access to all of the database objects referenced in the Omnidex Environment Files. |
| ===== ===== | ===== ===== | ||