Release Notes for the GM - InterBase ODBC Driver
- Transactions started using isc_start_multiple instead of isc_start_transaction now.
The va_arg list of isc_start_transaction sometimes caused access violations.
- Database connections to a local server on Win2000 work now.
- Connect/disconnect to/from local server is much faster now.
- SQLSpecialColumns, SQLStatistics and SQLDescribeParam implemented now.
- Works with MS-Query now. Updating data from MS-Query doesn't work.
- MS-Access can link tables now but thinks all rows are deleted when showing the data.
- ADO OLE-DB provider for ODBC works fine with the driver.
- Setup now build with NSIS.
- InterBase client installation included in the setup now.
- Complete source code included in the setup now.
- Some internal simplifications.
- Errors intoduced by latest changes fixed.
- More data type conversions supported by the driver now.
- Aggregate select functions MIN, MAX, AVG, SUM, COUNT give correct result set when executed on other cursors than SQL_CURSOR_FORWARD_ONLY.
- String input parameters are always correctly converted to InterBase now.
- If application buffers are too small the driver allocates its own buffers and translates data to application buffers now.
- Some internal simplifications done.
- Installation option for InterBase client driver added to Setup.
- SQLGetTYpeInfo Implemented now.
- SQLFreeXxxx / SQLAllocXxxx implemented again to support ODBC 2.0 applications.
- SQLGetData can be used even if there are no buffers bound by the application. Still the driver does not allocate own buffers if the application provides buffers via SQLBindCol.
- Parameters are supported now via SQLBindParameter or SQLParamData + SQLPutData.
- All data can be delivered as SQL_C_CHAR by the driver now (via SQLGetData and SQLBindCol). The driver will deliver a textual representation of the data in this case.
- All options for SQLFreeStmt implemnted now. This allows cursor reuse.
- Implementation of SQLTables now is sensitive to SQL_ATTR_METADATA_ID.
- Additional attributes supported by SQLGetInfo now.
- Registry value names changed. Existing DSN entries need to be recreated or edited once. The old settings of existing DSN entries will be forgotten.
- SQLDriverConnect parses the whole Connection String now. Values read by "DSN=XXX" are superseded by the values given in the connection string. The token "DSN=XXX" maybe omitted completely, but then the values given in the connection string should privde enough information for a successful connection. possible values are:
CharsetName=ISO8859_1 (ASCII, BIG_5, CYRL, DOS437, DOS850, DOS852, DOS857, DOS860, DOS861, DOS863, DOS865, EUCJ_0208, GB_2312, ISO8859_1, KSC_5601, NEXT, NONE, OCTETS, SJIS_0208, UNICODE_FSS, WIN1250, WIN1251, WIN1252, WIN1253, WIN1254)
LockGranularity=0 (lgRow = 0, lgTable = 1)
LockResolution=0 (lrWait = 0, lrFail = 1)
SQLDialect=3 (V5 = 1, V5/V6 = 2, V6 = 3)
WriteStrategy=0 (wsAllowAsyncWrites = 0, wsForceSyncWrites = 1)
- More ODBC attributes supported now.
- Browsing ADO client side cursors through the driver works now.
- Safe against invalid handles passed to the driver now.
- Uneccessary functions dropped from the driver.
- Bind offsets recognized by the driver now.
- Workaround for InterBase access violation with transactions on local server included.
- Debugging structures consuming large amounts of memory eliminated.
- A few minor code improvements/simplifications.
- Follows ODBC 3.0 standard.
- Thread safe.
- Direkt and partitioned BLOB update supported.
- All cursor types supported.
- Positioned update/insert/modify operations via SQLSetPos supported for all cursor types.
- Multiple errors in a single API call are all exposed by error diagnostic.
- Completely stable even against internal errors.
- Update of multi table queries possible.
- Lean but effective implementation results in high performance.
- Clear and understandable DSN setup dialog.
- Automatic increment of integer ID fields possible.
- Tested with InterBase 6.0/6.5.
- SQL parameters "?" are not supported.