|
|
|
|
|
|
|
|
|
|
- Overview
- Configuring a connection
- Remarks
- Date format returned by the native Oracle driver (5.5 compatibility)
- Options of a connection
- Options for the locks
- Connection test
Configuring the connection with WDORAINS (optional setting)
 Available only with this kind of connection
 Warning
For backward compatibility with the earlier versions of Native Oracle Connector (also called Native Oracle Access), the connection can still be configured in WDSQSINS (supplied with Native Oracle Connector).
WDORAINS can also be used to configure some specific options of the Native Connector. It is now recommended to use:
This software is supplied: - 32-bit: WDORAINS.EXE
- 64-bit: WDORAINS64.EXE
WDORAINS is no longer required since version 8 (and later). Reminder: WDORAINS connection settings need to be made only once. This page presents: To configure the connection: - Start WDORAINS (32-bit or 64-bit).
- In the window that opens (used to list the existing connections), click the "Add" button to create a new connection.
- Specify the connection settings:
- Choose the name of the data source. This name will be passed as a parameter to SQLConnect to connect to the database. If the connection was defined in the data model editor of WINDEV or WEBDEV, specify the name of the corresponding connection.
- Add a description caption
- Specify a connection string. This connection string will allow SQL*Net to find the database. This value must be supplied by the administrator of the Oracle database. Example connection string: "OracleServeur".. In this example, "OracleServer" is the alias to the server defined in SQL*Net.
- Specify whether the format of the dates must remain compatible with WinDev 5.5.
Reminder: Between version 5.5 and 5.5B, the date format returned has changed. If you check the box, you will restore the date format returned before version 5.5B (see the paragraph below). - Specify date format for INSERT and UPDATE queries: this option defines the default format used for dates in Text format.. This format will be used if the date format is not specified in the query.
- Specify the prefetch options for Oracle 8i or later.
Reminder: Oracle 8i retrieves records in blocks (operation called "prefetch"). A large block requires more memory but reduces the network traffic.- The number of records corresponds to the number of rows in each block.
- The maximum memory used corresponds to the size (in bytes) of each block. The "No limit" option allows you to specify no limit.
- Specify whether the distributed transactions must be used or not. By default, the distributed transactions are used by the locks and transactions handled by Native Oracle Connector. Check this option if:
- The distributed transactions are not supported by your server.
- The distributed transactions are not supported by the versions of client libraries (ORA_02041 error).
- The connection is added to the list once the parameters are validated.
Remarks - The information about the setting is stored in the .INI file in the directory of Windows.
- WDSQL is used to check whether the connection to the database is correct.
Date format returned by the native Oracle driver (5.5 compatibility) In version 5.5: The date returned by the native Oracle driver when reading a Date field was: DD-MM-YYYY. In version 5.5B: The date returned by the native Oracle driver when reading a Date field is now: YYYYMMDD. Reasons for modification: Harmonize date management in WINDEV. Simplifies the assignment of the date read by the Oracle driver in a WINDEV control of DATE type. No specific process is required to convert the date into a format recognized by WINDEV. How to keep the former operating mode? Set the date format returned in WDORAINS: simply check the "Compatibility: return dates in 'DD-MM-YYYY' format" box when describing the database used. Reminder: When writing to a database using the native Oracle driver, use the standard ODBC format {d 'YYYY-MM-DD'} (with a space between the d and ' ).. The driver automatically converts the date into the format used by the database. Example: INSERT INTO TABLE(DATE) VALUES ({d '1999-12-25'}) Remark: Since version 12, empty dates correspond to strings completed with 0s.. In the earlier versions, the empty dates corresponded to empty strings. Options for the locks - waiting: waiting when calling SQLLock can be infinite or not (blocking loop).
- the lock mode. For more details, see the documentation about the server.
Note: If the Oracle server version is lower than the Oracle client version (e.g. Oracle server 7.3 and Oracle client 8), certain malfunctions may occur.. To avoid these problems, check "Always use a 7.x client". To run the test of a connection from WDORAINS: - Select the connection whose test must be run.
- Click the "Test" button.
- Specify the name and password of the user.
- Click "Test connection". The status report is displayed.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|