Installation Instructions and Release Notes


To install the new driver:

-- copy NOTESSQL.EXE to a temporary directory (e.g. \temp)
-- from DOS, run NOTESSQL to expand the files.
-- from Windows, File Run \temp\setup to install the driver
-- delete the files from the temporary directory


Release Notes for NotesSQL 1.2

Feature Changes since v1.1d


Peformance Improvement for connection

 NotesSQL v1.2 reduces connection time substantially by doing
 incremental system catalog construction as the driver needs
 information about forms and views. At connection, the driver
 only opens the database and reads the names of forms and views.

Cacheing of buffers for subsequent execution of the same query

 NotesSQL now caches various internal buffers for successive
 executions of the same query or query using the same table.
 This improves performance for applications like Approach which
 do not cache query results in their internal buffers.



Problems and Limitations Addressed in this build

Input Translation Formulas

 NotesSQL can now handle more general cases of Input Translation
 formulas. Version 1.1 only allowed formulas having single expressions.

IS NULL and IS NOT NULL
 
 NotesSQL now handles these predicates consistently whether they are
 in Notes formulas or evaluated by the driver.  A field value is
 considered NULL either when the field does not exist in a Notes
 document or if it exists but has no content.

WHERE clause with join predicate

 NotesSQL had a problem with queries involving a join of two tables
 and an additional WHERE clause having inner and outer table columns.
 This problem has been fixed in v1.2.

Using NotesSQL with two instances of an application

 NotesSQL 1.1 introduced a problem where disconnecting from NotesSQL
 would affect other applications ability to call the driver.  The
 driver is now able to handle multiple concurrent connections.
 NotesSQL cannot support simultaneous database operations from more
 than one application because Notes V3 does not support this. 

Duplicate rows returned when collection buffer is reallocated

 This occurred in queries against views which generated a large
 result set and has been fixed in this release.

IS NULL Memory leak

 NotesSQL v1.1d left memory allocated after executing queries
 having IS NULL on date/time or numeric fields. This release fixes
 that problem.

Repeatedly calling SQLExecute with queries having WHERE clause

 If SQLExecute is called more than about 2000 times with queries
 that have a SELECT with a WHERE clause, NotesSQL v1.1d would run out
 of memory. If the query was more complicated, the problem would
 appear with fewer executions. The problem would not occur if the
 application periodically frees the statement handle and reallocated
 it.  NotesSQL v1.2 does not keep old buffers from SQLExecute and
 avoids this limitation.

"Column not Updatable" on Insert or Update 

 NotesSQL v1.2 returned the message "Column not Updatable" when
 inserting or updating on databases with large number of forms and
 views.  It has been fixed by the incremental catalog construction
 strategy adopted in Release 1.2.

Modification of forms generated by CREATE TABLE

 Because of a problem with forms generated by NotesSQL CREATE TABLE
 statement, you could not change fonts in paragraphs in these forms.
 The workaround was to copy fields to new paragraphs and change fonts.
 Forms created by NotesSQL 1.2 allow fonts to be changed from Notes.

Subqueries in SELECT with operators

 This release fixes a problem with the result from a SELECT subquery
 which joins outer and inner using operators like,  =,  or >=,
 without ANY, ALL etc.


