This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:oracle:environments [2011/04/06 22:30] doc |
integration:rdbms:oracle:environments [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 83: | Line 83: | ||
| * Oracle National Character datatypes, which are commonly used to store Unicode data, are shown as CHARACTER or STRING datatype, as these are the most universal datatypes in an Omnidex application. If necessary, these can be changed to Omnidex NCHARACTER or NSTRING datatypes. | * Oracle National Character datatypes, which are commonly used to store Unicode data, are shown as CHARACTER or STRING datatype, as these are the most universal datatypes in an Omnidex application. If necessary, these can be changed to Omnidex NCHARACTER or NSTRING datatypes. | ||
| * Depending on the configuration of the Oracle database, some constraint information may not be available and must be added manually. | * Depending on the configuration of the Oracle database, some constraint information may not be available and must be added manually. | ||
| + | |||
| + | === Manually Creating an Omnidex Environment File === | ||
| + | |||
| + | An Omnidex Environment File can also be created by manually issuing CREATE ENVIRONMENT, CREATE DATABASE, CREATE TABLE and CREATE INDEX statements in OdxSQL or using ODBC or JDBC. If these statements are written to a text batch file, then that file can be submitted to OdxSQL using the USE command. | ||
| + | |||
| ===== ===== | ===== ===== | ||