home *** CD-ROM | disk | FTP | other *** search
- Release Notes
- InterClient 1.12
- Last modified: Nov 10, 1997
-
- Contents:
- I. Differences with 1.0 release
- II. Issues
-
- __________________________________________________________________
- Differences with 1.0 release
-
- * The remote protocol layer for JDBC/Net communication
- between InterClient and InterServer has changed in this release.
- Therefore, this release of InterClient will not interoperate with
- previous releases of InterServer, and vice-versa.
-
- * A new interbase.interclient.ExpiredDriverWarning class has been
- added that extends java.sql.SQLWarning.
- An expired InterClient driver will no longer refuse connections,
- rather connections established after the expiration date
- are tagged with the SQLWarning ExpiredDriverWarning.
-
- * The NT registry settings location has changed from
- Software\InterBase\InterClient
- to
- Software\InterBase Corp\InterClient
-
- This change was made to match the InterBase product registry
- location of
- Software\InterBase Corp\InterBase
-
- * The Windows install now modifies the JBuilder.INI file, if
- present, to include InterClient on its local ClassPath and
- IDEClassPath environment variables.
-
- * The Windows help system for InterClient has been replaced by
- an HTML based help to allow for cross-platform implementation.
-
- * The behavior of escaped procedure calls has been extended
- to allow for both InterBase "executable procedures" and
- "select procedures", see the API reference documentation
- for class CallableStatement.
-
- * Various bug fixes and documentation changes.
-
- * InterBase and InterClient information is now available
- via a newsgroup monitored by InterBase. Set your reader to
- forums.borland.com/borland.public.interbase.
- Bug reports may be submitted to icsupport@interbase.com
-
- __________________________________________________________________
- Issues
-
- Please be aware of the following issues affecting this release of
- InterClient:
-
- * Running InterClient applets requires a JRE 1.1 enabled browser.
- Installing the JDBC driver manager on the client machine is no
- longer necessary since JDBC is integrated with JRE 1.1 in the
- package java.sql.
- The interclient.jar archive (or class files) includes a CommDiag
- utility which uses the AWT 1.1 event model, run
-
- java interbase.interclient.utils.CommDiag
-
- * When testing your installation with the appletviewer:
- unset CLASSPATH
- appletviewer CommDiag.html
- Make sure your CLASSPATH environment variable does NOT include
- interclient.jar or the interclient classes directory.
- Either occurrence will cause a java.lang.IllegalAccessError.
- Temporarily unset CLASSPATH in your DOS session before
- invoking appletviewer on a local html file.
-
- * If you reference the local CommDiag.html thru a browser, you
- may need to remove interclient.jar from your CLASSPATH to avoid
- certain security exceptions with the Netscape browser.
-
- * The Java archive file interclient.jar is not digitally signed
- by the InterBase Software Corporation. Vendors writing Java applets
- that work with InterClient should digitally sign their applets
- and the interclient.jar file with their identity for use with
- Netscape Communicator.
-
- * BLOb stream data from ResultSet.getAsciiStream and getBinaryStream
- is not buffered internally by InterClient.
- This provides application programs the flexibility to read directly
- from the java socket input stream. Be sure to understand
- how to read from Java input streams efficiently; in particular
- understand that reading one byte at a time on a Java socket
- is much less efficient than reading large chunks of data.
-
- * If you had previously installed a 0.7x release,
- then be sure your services file is updated.
- The port for the interserver service has changed from 3051 to 3060.
- See the InterClient README.TXT file for instructions on changing
- your system's services file.
-
- * If the database being accessed contains security classes created
- using the InterBase V3.3 tool GDEF, certain methods which return
- privilege related information may return incorrect results, e.g.,
- areAllTablesSelectable. This is only an issue for InterBase
- customers who have versions of InterBase prior to V4.0 and are
- migrating to V4.0. GDEF functionality was frozen in V3.3 and is
- no longer supported in V4.0.
-
- Please note, in all cases, the security defined is enforced correctly,
- i.e., if a user does not have appropriate privilege to perform a
- certain operation, the operation will not be performed.
-
- * DatabaseMetadata.getProcedureColumns returns 0 for precision values
- for NUMERIC and DECIMAL columns rather than the correct precision.
-
- * DatabaseMetadata.getColumns does not return the proper default value
- of a column in an InterBase table.
-
- * See JBuilderNotes.txt for information on using InterClient
- with JBuilder.
-
- ---------------------------------END----------------------------------
-