This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:mysql:databases [2011/04/05 20:25] doc |
integration:rdbms:mysql: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 MySQL database within an Omnidex Environment File. This statement can either be issued directly, or it can be extracted from MySQL 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 MySQL database within an Omnidex Environment File. This statement can either be issued directly, or it can be extracted from MySQL using the EXTRACT statement as discussed in the previous section. |
| - | The CREATE DATABASE statement must include the database name and the MySQL user and password. | + | The CREATE DATABASE statement must include the DSN or File DSN that identifies the MySQL database, as well as the MySQL 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. Note that the database type is ODBC, with a subtype of MYSQL, reflecting that ODBC is the primary method of accessing a MySQL database. |
| - | Note that the datatype type is ODBC, with a subtype of MYSQL, reflecting that ODBC is the primary method of accessing a MySQL database. | + | |
| <code> | <code> | ||
| Line 30: | Line 29: | ||
| type odbc | type odbc | ||
| subtype mysql | subtype mysql | ||
| + | dsn "simple" | ||
| user "simple" | user "simple" | ||
| password "simple" | password "simple" | ||
| Line 38: | Line 38: | ||
| === MySQL Security === | === MySQL Security === | ||
| - | Omnidex provides two methods of supporting MySQL security. The first option is for administrators to register a single user and password in the Omnidex Environment File to access a MySQL database. The second option is to pass a user and password in the [[dev:connections:home|Omnidex Connection String]]. This use user and password will be passed directly to MySQL to access the database. Administrators should insure that the user and password provides access to all of the database objects referenced in the Omnidex Environment Files. | + | Omnidex provides three methods of supporting MySQL security. |
| + | |||
| + | * Administrators can register a user and password in the MySQL datasource. | ||
| + | * Administrators can register a user and password in the Omnidex Environment File. This user and password will always be used to access the MySQL 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 MySQL to access the database. | ||
| + | |||
| + | One of these approaches must be used to allow connections to the MySQL database. Administrators should insure that the user and password provides access to all of the database objects referenced in the Omnidex Environment Files. | ||
| ===== ===== | ===== ===== | ||