|
|
|
The following new features provide connectivity enhancements.
|
|
|
Support for the JDBC 3.0 API includes three components: an installation server, a Java client driver, and an information utility. For more information, see the Connectivity Guide.
|
|
|
The Data Access Server (DAS) runs as part of a standard Ingres installation. The DAS translates JDBC requests from the Ingres JDBC Driver into Ingres internal format and forwards the request to the appropriate DBMS Server. The DAS supports the same network protocols and port designations as the Communications Server.
The DAS also supports the new Ingres .NET Data Provider component that enables high-performance native .NET access to Ingres data sources and delivers Ingres data to the Microsoft .NET Framework.
Through the DAS, a JDBC client and Ingres .NET Data Provider have full access to Ingres, Enterprise Access, and EDBC databases. The DAS can also access database servers on remote machines using Ingres Net.
For more information, see the Connectivity Guide.
|
|
|
The Ingres JDBC Driver is a pure Java implementation of the JDBC 3.0 API released with the Sun Java 2 SDK, version 1.4. The driver supports application, applet, and servlet access to Ingres data sources through the Data Access Server.
The JDBC driver provided in Ingres 2.6 continues to be supported in Ingres 2006. For migration instructions related to the JDBC driver, see the Migration Guide.
The Ingres JDBC Driver with the DAS supports the following JDBC 3.0 features:
The Ingres JDBC Driver is delivered as a single Java archive file, iijdbc.jar, located in the library directory (lib) of the Ingres installation. Access to the driver can require, depending on the Java environment used, adding the Java archive to the CLASSPATH environment setting or as a resource in the appropriate utility. For browser/applet access, the Java archive must be copied to the Web Server directories.
|
|
|
The JDBC 3.0 API support includes a JDBC information utility, JdbcInfo. This utility displays the Ingres JDBC Driver internal release information. The class files for the JdbcInfo utility are located in the library directory (lib) of the Ingres installation.
For more information, see the Connectivity Guide.
|
|
|
The Ingres JDBC driver supports updateable result set features of the JDBC 2.1 API. Updateable result sets permit an application to update or delete the current row of the result set, or insert rows into the associated table using methods provided by the JDBC ResultSet class. A new class, RsltUpdt, has been added as an extension to the cursor result set class, RsltCurs, to support updateable result sets. The result set methods associated with the RsltUpdt class are listed below.
The ability to update a result set is determined by calling the following method:
ResultSet.getConcurrency()
The current row of a result set can be deleted using the following method:
ResultSet.deleteRow()
Columns values of the current row can be set using the following methods:
ResultSet.updateAsciiStream()
ResultSet.updateBigDecimal()
ResultSet.updateBinaryStream()
ResultSet.updateBoolean()
ResultSet.updateByte()
ResultSet.updateBytes()
ResultSet.updateCharacterStream()
ResultSet.updateDate()
ResultSet.updateDouble()
ResultSet.updateFloat()
ResultSet.updateInt()
ResultSet.updateLong()
ResultSet.updateNull()
ResultSet.updateObject()
ResultSet.updateShort()
ResultSet.updateString()
ResultSet.updateTime()
ResultSet.updateTimestamp()
Once column values have been set, the changes can be saved or dropped using the following methods:
ResultSet.updateRow()
ResultSet.cancelRowUpdates()
To insert a row, the result set current position must be moved to a special reserved row. The following methods control the positioning of the result set and the insertion of rows:
ResultSet.moveToInsertRow()
ResultSet.moveToCurrentRow()
ResultSet.insertRow()
The following methods can be used to determine the status of a result set row:
ResultSet.rowDeleted()
ResultSet.rowInserted()
ResultSet.rowUpdated()
For more information, see the Connectivity Guide.
|
|
|
This release of Ingres introduces support for the Microsoft .NET Framework and Visual Studio .NET application development tools.
|
|
|
The Ingres .NET Data Provider is a .NET component that enables high-performance native .NET access to Ingres data sources and delivers Ingres data to the Microsoft .NET Framework.
The Ingres .NET Data Provider offers a series of .NET types to describe the user's data, .NET provider classes to manipulate the data, and connection pooling to efficiently manage data connections.
The design and naming conventions of the Ingres .NET Data Provider's data types, classes, properties, and methods follow the same pattern as the Microsoft .NET Data Providers. Consequently, developers who are familiar with the Microsoft providers can easily develop or convert existing code from Microsoft databases to Ingres databases.
All Ingres .NET Data Provider modules are written in C#, a managed .NET language with full access to every .NET Framework capability. Even though the data provider is written in C#, any managed language such as VB.NET or J# can use the data provider because of .NET's language interoperability feature.
For more information, see the Connectivity Guide.
|
|
|
The .NET Framework was written with design-time support. Integration with the Visual Studio .NET visual tools allows programmers to drag-and-drop the Ingres .NET Data Provider design component onto a design surface such as a the Windows Form Control (WinForm). Integration also includes the following design components:
For more information, see the Connectivity Guide.
|
|
|
Prior to this release, ODBC users on non-Windows platforms were required to manually edit the odbc.ini configuration file to define a data source. This release introduces an Ingres ODBC Administrator utility for non-Windows platforms. Supported platforms include UNIX, Linux, and VMS. The new ODBC Administrator enables users to:
For more information, see the Connectivity Guide.
|
|
|
This release provides a new Windows TCP/IP protocol driver that takes advantage of the latest Windows Winsock 2.2 API. The new driver (tcp_ip) removes an architectural limitation of the previous implementation (wintcp), which resulted in a performance problem when a client application used many INSERT statements or a large number of single SELECT statements. Also, connection attempts sometimes failed when multiple connects were attempted simultaneously.
To allow a smooth migration from the existing protocol driver to the new one, the existing wintcp protocol driver is included in this release, but will be removed in the future. We recommend that you use the tcp_ip protocol driver.
For more information, see the Connectivity Guide.
|
|
|
The Ingres ODBC Call-level Interface (CLI) provides access to the ODBC application environment without the need to use third-party software. It is installed when you install the Ingres ODBC Driver and is supported on all platforms on which Ingres runs.
The Ingres ODBC CLI performs the following functions:
For more information, see the Connectivity Guide and the System Administrator Guide.