Kbase 20810: Can tables from two databases be Joined using SQL-89 & SQL-92?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/24/2008 |
|
Status: Verified
GOAL:
Can tables from two databases be Joined using SQL-92?
GOAL:
Can tables from two databases be Joined using SQL-89?
GOAL:
Can you do a join of tables in different databases using SQL-92?
GOAL:
Can you do a join of tables in different databases using SQL-89?
GOAL:
Is it possible to join tables from different databases using SQL-92?
GOAL:
Is it possible to join tables from different databases using SQL-89?
GOAL:
How to access tables from different databases using SQL-92
GOAL:
How to access tables from different databases using SQL-89
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Versions
FIX:
The MERANT Version 3.6 DataDirect ODBC driver allows multiple SQL-89 Progress database connections from one data source with Progress Versions 7, 8, and 9.
The DataDirect ODBC driver replaces the MERANT Version 3.5 which uses the Progress SQL-89 engine.
This connectivity was not possible with Progress SQL-92 until OpenEdge 10.1A.
Starting on 10.1B, multi-database queries are supported. This means that it is now possible to join tables from different databases using SQL-92.
Using the Progress SQL-89 engine, when an initial connection is established, the DataDirect 3.6 ODBC driver passes the multiple database connection parameters to the Open Interface Broker (OIB). The OIB starts an Open Interface Driver (OID) for the connection and passes the database connection parameters to it. The OID is in effect a 4GL client with a different user interface. It handles connections to multiple Progress databases just as a Progress 4GL client does. Here, the OID handles joins across multiple databases and passes a single result set back to the ODBC driver. A connectivity quirk when using Progress 4GL and SQL-89 can work to a users advantage. Here, the OID acts as middleware that performs a join across multiple databases and makes separate queries. It is, however, invisible to the ODBC driver and ODBC client application.
Un