Directives and Dialects

Dialog System V2.5

Chapter 7: Embedded SQL Toolkit

This chapter lists differences in OpenESQL compared to Embedded SQL Toolkit for Microsoft SQL Server.

7.1 Summary of Changes

SQL(MSSQL) NOSQLDB NOSQLPASS NOSQLACCESS

SQL(DBMAN=ODBC,TARGETDB=MSSQLSERVER,NOACCESS) 

SQL(MSSQL) SQLDB(server.database)
    SQLPASS(user.pwd) SQLINIT

SQL(DBMAN=ODBC,TARGETDB=MSSQLSERVR, DB=datasourcename.db,PASS=user.pwd,INIT=PROT)

SQL(MSSQL)SQLPROT

SQL(DBMAN=ODBC,TARGETDB=MSSQLSERVER, INIT=PROT)

Other differences are:

• The SQL Server bit data type is not supported.

• BROWSE mode cursors are not supported. The cursor support available is of a higher level. Where possible, BROWSE mode syntax is mapped to the new cursor support.

• You cannot EXECUTE IMMEDIATE on a stored procedure. Instead, use EXEC SQL EXEC stored_procedure END-EXEC

• The text of some error messages has changed. Where possible the SQLCODE and SQLSTATE are the same as before.

• Returning a SQL Server CHAR column into an Embedded SQL INTEGER field gives different results.

• Cursors are closed on a COMMIT, instead of remaining OPEN. The new behavior is consistent with an ANSI implementation.

• Doing a COMMIT on an empty transaction does not return an error status.

• A COMPUTE statement is not allowed in a cursor declaration.

• DATETIME fields are returned in a different format. You can insert in the same format as with the Embedded SQL Toolkit, but data is returned in YYYY-MM-DD format. This is the only format the ODBC driver supports.

• Use of DISTINCT in a cursor declaration makes the cursor READ ONLY.

• FETCHBUFFER of size 1 is the only size supported in this release.

• Positioning a DELETE on a row that no longer exists gives a error status rather than SQLCODE = 100 ("End of results").

• SCROLLOPTION MIXEDn is not supported.

• The use of '??' as a marker for binary data is supported for backward compatibility. It should not be used in new applications.

Directives and Dialects

Dialog System V2.5