This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
integration:rdbms:mysql:databases [2011/04/05 02:53] 127.0.0.1 external edit |
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, the MySQL version, 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. |
| - | + | ||
| - | <code> | + | |
| - | create database "SIMPLE" | + | |
| - | type mysql | + | |
| - | version "11" | + | |
| - | user "simple" | + | |
| - | password "simple" | + | |
| - | index_directory "idx" | + | |
| - | in "simple.xml"; | + | |
| - | </code> | + | |
| - | + | ||
| - | === Using SQL*Net === | + | |
| - | + | ||
| - | Omnidex is frequently installed on a separate server than the MySQL database. In fact, this is preferable since it allows both Omnidex and MySQL to operate at their best without competing for resources. This means that Omnidex often accesses the MySQL database through SQL*Net. When using SQL*Net, simply state the name of the SQL*Net service in the SERVICE clause. | + | |
| <code> | <code> | ||
| Line 43: | Line 29: | ||
| type odbc | type odbc | ||
| subtype mysql | subtype mysql | ||
| + | dsn "simple" | ||
| user "simple" | user "simple" | ||
| password "simple" | password "simple" | ||
| - | service "simple" | ||
| index_directory "idx" | index_directory "idx" | ||
| in "simple.xml"; | in "simple.xml"; | ||
| Line 52: | Line 38: | ||
| === MySQL Security === | === MySQL Security === | ||
| - | Omnidex uses a single user and password to access an MySQL database. MySQL database administrators should provide an appropriate user and password that gives access to all of the database objects referenced in the Omnidex Environment Files. | + | Omnidex provides three methods of supporting MySQL security. |
| - | When connecting to an Omnidex Environment File, it is generally not possible to pass different user and passwords dynamically; however, there is an exception to this rule. The user and password can reference [[appendix:reference:envvar:home|environment variables or shell commands]]. This can provide a rudimentary mechanism for providing dynamic users and passwords. Care should be taken when using this approach, though. All users passed should have access to all database objects declared in the Omnidex Environment File, and should also have access to all rows in the tables. | + | * 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. | ||
| ===== ===== | ===== ===== | ||