## 1 ODBC Release Notes

This document describes the changes made to the odbc application.

### 1.1 ODBC 2.0.8

#### 1.1.1 Improvements and New Features

- Minor Makefile changes.
  Own Id: OTP-6689

### 1.2 ODBC 2.0.7

#### 1.2.1 Fixed Bugs and Malfunctions

- When using a parameterized query on a windows platform the data was inserted in the table on the sql-server but the connection was lost, this seems to be due to a compiler error that has now been worked around, but further investigation is ongoing to verify that that really was the problem.
  Own Id: OTP-5504
- param_query/[3,4] could return an unexpected row count for some drivers, in this case a postgresdriver.
  Own Id: OTP-6363

### 1.3 ODBC 2.0.6

#### 1.3.1 Fixed Bugs and Malfunctions

- pthread header and library mismatch on linux systems (at least some SuSE and Debian) with both NPTL and Linuxthreads libraries installed.
  Own Id: OTP-5981

#### 1.3.2 Improvements and New Features

- Changed configure to find odbc in /usr/local too
  Own Id: OTP-5966

#### 1.3.3 Known Bugs and Problems

- When using a parameterized query on a windows platform the data is inserted in the table on the sql-server but for some reason the connection is lost.
  Own Id: OTP-5504

### 1.4 ODBC 2.0.5

#### 1.4.1 Fixed Bugs and Malfunctions

- Fixed bug, reported error when deleting nonexisting rows, thanks to Laura M. Castro for reporting this.
  Own Id: OTP-5759

#### 1.4.2 Known Bugs and Problems

- When using a parameterized query on a windows platform the data is inserted in the table on the sql-server but for some reason the connection is lost.
  Own Id: OTP-5504

### 1.5 Odbc 2.0.4

#### 1.5.1 Improvements and New Features

- /usr was added as a default place for configure to look for the odbc library on unix/linux platforms.
  Own Id: OTP-5501
- A legacy timer in the c port program was set to infinity. All timeout handling is handled by the erlang code and a extra timeout in the c code will just lead to confusion if it is released.
  Own Id: OTP-5502

#### 1.5.2 Known Bugs and Problems

- When using a parameterized query on a windows platform the data is inserted in the table on the sql-server but for some reason the connection is lost.
  Own Id: OTP-5504

### 1.6 Odbc 2.0.3

#### 1.6.1 Improvements and New Features

- odbc now uses configure as all "normal" applications instead of providing special Makefiles for each commercial supported platform. This also makes it easier to build odbc on non supported platforms.
  Own Id: OTP-5437

### 1.7 odbc 2.0.2

#### 1.7.1 Fixed Bugs and Malfunctions

- When issuing a batch of queries and one of the queries fail the odbc port program crashed. This is no longer the case.
  Own Id: OTP-5176

### 1.8 odbc 2.0.1

#### 1.8.1 Improvements and New Features

- Added use of the socket option TCP_NODELAY, as in the case of Erlang odbc the Nagel algorithm will never help, but always cause an unnecessary delay.
  Own Id: OTP-5100

### 1.9 odbc 2.0

#### 1.9.1 Improvements and New Features

- Erlang ODBC now handles batches of queries and can return multiple result sets.
  Own Id: OTP-4642 Aux Id: seq7766
- The old interface that became deprecated in odbc 1.0 has now been removed.
  *** POTENTIAL INCOMPATIBILITY ***
  Own Id: OTP-4794
- The port program now sends different exit codes to Erlang when it exits due to failure. This instead of sending the same exit code and then trying to write to stderr. Erlang encodes the exit code to a descriptive atom.
  Own Id: OTP-4813
- Erlang ODBC now supports parameterized queries for the most common ODBC data types.
  Own Id: OTP-4821
- SQL_NUMERIC and SQL_DECIMAL columns are converted to integer and float values if possible.
  *** POTENTIAL INCOMPATIBILITY ***
  Own Id: OTP-4826
- Result sets are now by default returned as a list of tuples which is the most intuitive and useful mapping. To keep some degree of backwards compatibility you may turn this off to get the old behavior that result sets are returned as lists of lists. However do not use this in new code as it is considered a deprecated feature that eventually will disappear.
  *** POTENTIAL INCOMPATIBILITY ***
  Own Id: OTP-4850
- The odbc implementation now mostly uses sockets to communicate between the c and the erlang process, this is to avoid a lot of problems arising from different odbc-drivers doing strange things that disturbed the port-program communication mechanism.
  Own Id: OTP-4875

For information about older versions see release notes history.

odbc 2.0.8
Copyright © 1991-2007 Ericsson AB