The R13B03 release.OTP_R13B03

1 files changed, 492 insertions, 0 deletions

diff --git a/lib/odbc/doc/src/notes.xml b/lib/odbc/doc/src/notes.xml
new file mode 100644
index 0000000000..1f9b3b4290
--- /dev/null
+++ b/lib/odbc/doc/src/notes.xml
@@ -0,0 +1,492 @@
+<?xml version="1.0" encoding="latin1" ?>
+<!DOCTYPE chapter SYSTEM "chapter.dtd">
+
+<chapter>
+  <header>
+    <copyright>
+      <year>2004</year><year>2009</year>
+      <holder>Ericsson AB. All Rights Reserved.</holder>
+    </copyright>
+    <legalnotice>
+      The contents of this file are subject to the Erlang Public License,
+      Version 1.1, (the "License"); you may not use this file except in
+      compliance with the License. You should have received a copy of the
+      Erlang Public License along with this software. If not, it can be
+      retrieved online at http://www.erlang.org/.
+    
+      Software distributed under the License is distributed on an "AS IS"
+      basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
+      the License for the specific language governing rights and limitations
+      under the License.
+    
+    </legalnotice>
+
+    <title>ODBC Release Notes</title>
+    <prepared>otp_appnotes</prepared>
+    <docno>nil</docno>
+    <date>nil</date>
+    <rev>nil</rev>
+    <file>notes.xml</file>
+  </header>
+  <p>This document describes the changes made to the odbc application.
+  </p>
+
+  <section><title>ODBC 2.10.6</title>
+
+    <section><title>Fixed Bugs and Malfunctions</title>
+      <list>
+        <item>
+          <p>
+            Applied a patch from Andrew Thompson, which fixes some
+            error cases.</p>
+          <p>
+            Own Id: OTP-8291</p>
+        </item>
+      </list>
+    </section>
+
+
+    <section><title>Improvements and New Features</title>
+      <list>
+        <item>
+          <p>
+            The documentation is now built with open source tools
+            (xsltproc and fop) that exists on most platforms. One
+            visible change is that the frames are removed.</p>
+          <p>
+            Own Id: OTP-8250</p>
+        </item>
+      </list>
+    </section>
+
+  </section>
+
+  <section><title>ODBC 2.10.5</title>
+  
+  <section><title>Fixed Bugs and Malfunctions</title>
+  <list>
+    <item>
+      <p>
+      A missing return statement in a non void function has been fixed in <c>odbc</c>. (Thanks to Nico Kruber)
+      </p>
+      <p>
+      Own Id: OTP-7978</p>
+    </item>
+  </list>
+  </section>
+  
+  </section>
+
+
+  <section><title>ODBC 2.10.4</title>
+  
+  <section><title>Improvements and New Features</title>
+  <list>
+    <item>
+      <p>
+	param_query now handles the in_or_out parameter
+      correctly.</p>
+      <p>
+      Own Id: OTP-7720</p>
+    </item>
+    <item>
+      <p>
+	Changed the internal socket use so that it will become
+      more robust to non-functional ipv6 and fallback on ipv4.</p>
+      <p>
+      Own Id: OTP-7721</p>
+    </item>
+  </list>
+  </section>
+  
+  </section>
+
+ <section><title>ODBC 2.10.3</title>
+
+    <section><title>Improvements and New Features</title>
+      <list>
+        <item>
+          <p>
+            Configure update for mac.</p>
+          <p>
+            Own Id: OTP-7418</p>
+        </item>
+      </list>
+    </section>
+
+
+    <section><title>Known Bugs and Problems</title>
+      <list>
+        <item>
+          <p>
+            describe_table/[2,3] on mac gives an empty result</p>
+          <p>
+            Own Id: OTP-7478</p>
+        </item>
+      </list>
+    </section>
+
+</section>
+
+  <section><title>ODBC 2.10.2</title>
+  
+    <section><title>Fixed Bugs and Malfunctions</title>
+      <list>
+        <item>
+          <p>
+            SQLINTEGERs where not retrieved correctly on 64 bit
+            platforms as an SQLINTEGER is defined to be a 32 bit
+            integer and not a true long.</p>
+          <p>
+            Own Id: OTP-7297</p>
+        </item>
+      </list>
+    </section>
+
+  </section>
+  
+  <section><title>ODBC 2.10.1</title>
+  
+    <section><title>Improvements and New Features</title>
+      <list>
+        <item>
+          <p>
+            Now supports out and input parameters for stored
+            procedures.</p>
+          <p>
+            Own Id: OTP-7019</p>
+        </item>
+        <item>
+          <p>
+            ODBC is now prebuilt for SLES10 in the commercial build
+            and parameters to error_logger:error_report/1 has been
+            corrected.</p>
+          <p>
+            Own Id: OTP-7294</p>
+        </item>
+        <item>
+          <p>
+            Parametrized queries will now work correctly when using
+            Erlang R12B-2 on Linux (SuSE 10.3), MySQL 5.0.45, myodbc
+            3.51 and unixODBC 2.2.12. Earlier it could happen that an
+            error was returned even though data was correctly
+            inserted into the database.</p>
+          <p>
+            Own Id: OTP-7307</p>
+        </item>
+      </list>
+    </section>
+
+
+    <section><title>Known Bugs and Problems</title>
+      <list>
+        <item>
+          <p>
+            SQLINTEGERs are not retrieved correctly on 64 bit
+            platforms as an SQLINTEGER seems to be defined to be a 32
+            bit integer and not a true long.</p>
+          <p>
+            Own Id: OTP-7297</p>
+        </item>
+      </list>
+    </section>
+
+ </section>
+
+  <section><title>ODBC 2.10</title>
+    
+    <section><title>Improvements and New Features</title>
+      <list>
+        <item>
+          <p>
+            Enhanced configure to among other things work better when
+            there is a library found but it is not usable e.i. 32 bit
+            library in 64 bit build.</p>
+          <p>
+            Own Id: OTP-7062</p>
+        </item>
+      </list>
+    </section>
+    
+  </section>
+
+  <section><title>ODBC 2.0.9</title>
+    
+    <section><title>Improvements and New Features</title>
+      <list>
+        <item>
+          <p>
+            The odbc application now has to be explicitly started and
+            stopped e.i. it will not automatically be started as a
+            temporary application as it did before. Although a
+            practical feature when testing things in the shell, it is
+            not desirable that people take advantage of this and not
+            start the odbc application in a correct way in their
+            products. Added functions to the odbc API that calls
+            application:start/stop.</p>
+          <p>
+            *** POTENTIAL INCOMPATIBILITY ***</p>
+          <p>
+            Own Id: OTP-6984</p>
+        </item>
+        <item>
+          <p>
+            Changed Makefile.in so that odbc is not disabled on
+            64-bits architectures. It was earlier disabled due to
+            that it had never been tested in that environment.</p>
+          <p>
+            Own Id: OTP-6987</p>
+        </item>
+      </list>
+    </section>
+    
+  </section>
+  
+  <section>
+    <title>ODBC 2.0.8</title>
+
+    <section>
+      <title>Improvements and New Features</title>
+      <list type="bulleted">
+        <item>
+          <p>Minor Makefile changes.</p>
+          <p>Own Id: OTP-6689</p>
+        </item>
+      </list>
+    </section>
+  </section>
+
+  <section>
+    <title>ODBC 2.0.7</title>
+
+    <section>
+      <title>Fixed Bugs and Malfunctions</title>
+      <list type="bulleted">
+        <item>
+          <p>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.</p>
+          <p>Own Id: OTP-5504</p>
+        </item>
+        <item>
+          <p>param_query/[3,4] could return an unexpected row count
+            for some drivers, in this case a postgresdriver.</p>
+          <p>Own Id: OTP-6363</p>
+        </item>
+      </list>
+    </section>
+  </section>
+
+  <section>
+    <title>ODBC 2.0.6</title>
+
+    <section>
+      <title>Fixed Bugs and Malfunctions</title>
+      <list type="bulleted">
+        <item>
+          <p>pthread header and library mismatch on linux systems (at
+            least some SuSE and Debian) with both NPTL and
+            Linuxthreads libraries installed.</p>
+          <p>Own Id: OTP-5981</p>
+        </item>
+      </list>
+    </section>
+
+    <section>
+      <title>Improvements and New Features</title>
+      <list type="bulleted">
+        <item>
+          <p>Changed configure to find odbc in /usr/local too</p>
+          <p>Own Id: OTP-5966</p>
+        </item>
+      </list>
+    </section>
+
+    <section>
+      <title>Known Bugs and Problems</title>
+      <list type="bulleted">
+        <item>
+          <p>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.</p>
+          <p>Own Id: OTP-5504</p>
+        </item>
+      </list>
+    </section>
+  </section>
+
+  <section>
+    <title>ODBC 2.0.5</title>
+
+    <section>
+      <title>Fixed Bugs and Malfunctions</title>
+      <list type="bulleted">
+        <item>
+          <p>Fixed bug, reported error when deleting nonexisting rows,
+            thanks to Laura M. Castro for reporting this.</p>
+          <p>Own Id: OTP-5759</p>
+        </item>
+      </list>
+    </section>
+
+    <section>
+      <title>Known Bugs and Problems</title>
+      <list type="bulleted">
+        <item>
+          <p>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.</p>
+          <p>Own Id: OTP-5504</p>
+        </item>
+      </list>
+    </section>
+  </section>
+
+  <section>
+    <title>Odbc 2.0.4</title>
+
+    <section>
+      <title>Improvements and New Features</title>
+      <list type="bulleted">
+        <item>
+          <p>/usr was added as a default place for configure to look
+            for the odbc library on unix/linux platforms.</p>
+          <p>Own Id: OTP-5501</p>
+        </item>
+        <item>
+          <p>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.</p>
+          <p>Own Id: OTP-5502</p>
+        </item>
+      </list>
+    </section>
+
+    <section>
+      <title>Known Bugs and Problems</title>
+      <list type="bulleted">
+        <item>
+          <p>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.</p>
+          <p>Own Id: OTP-5504</p>
+        </item>
+      </list>
+    </section>
+  </section>
+
+  <section>
+    <title>Odbc 2.0.3</title>
+
+    <section>
+      <title>Improvements and New Features</title>
+      <list type="bulleted">
+        <item>
+          <p>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.</p>
+          <p>Own Id: OTP-5437</p>
+        </item>
+      </list>
+    </section>
+  </section>
+
+  <section>
+    <title>odbc 2.0.2</title>
+
+    <section>
+      <title>Fixed Bugs and Malfunctions</title>
+      <list type="bulleted">
+        <item>
+          <p>When issuing a batch of queries and one of the queries
+            fail the odbc port program crashed. This is no longer the
+            case.</p>
+          <p>Own Id: OTP-5176</p>
+        </item>
+      </list>
+    </section>
+  </section>
+
+  <section>
+    <title>odbc 2.0.1</title>
+
+    <section>
+      <title>Improvements and New Features</title>
+      <list type="bulleted">
+        <item>
+          <p>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.</p>
+          <p>Own Id: OTP-5100</p>
+        </item>
+      </list>
+    </section>
+  </section>
+
+  <section>
+    <title>odbc 2.0</title>
+
+    <section>
+      <title>Improvements and New Features</title>
+      <list type="bulleted">
+        <item>
+          <p>Erlang ODBC now handles batches of queries and can return
+            multiple result sets.</p>
+          <p>Own Id: OTP-4642 Aux Id: seq7766 </p>
+        </item>
+        <item>
+          <p>The old interface that became deprecated in odbc 1.0 has
+            now been removed.</p>
+          <p>*** POTENTIAL INCOMPATIBILITY ***</p>
+          <p>Own Id: OTP-4794</p>
+        </item>
+        <item>
+          <p>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.</p>
+          <p>Own Id: OTP-4813</p>
+        </item>
+        <item>
+          <p>Erlang ODBC now supports parameterized queries for the
+            most common ODBC data types.</p>
+          <p>Own Id: OTP-4821</p>
+        </item>
+        <item>
+          <p>SQL_NUMERIC and SQL_DECIMAL columns are converted to
+            integer and float values if possible.</p>
+          <p>*** POTENTIAL INCOMPATIBILITY ***</p>
+          <p>Own Id: OTP-4826</p>
+        </item>
+        <item>
+          <p>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.</p>
+          <p>*** POTENTIAL INCOMPATIBILITY ***</p>
+          <p>Own Id: OTP-4850</p>
+        </item>
+        <item>
+          <p>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.</p>
+          <p>Own Id: OTP-4875</p>
+        </item>
+      </list>
+    </section>
+    <!-- p>For information about older versions see
+      <url href="part_notes_history_frame.html">release notes history</url>.</p -->
+  </section>
+</chapter>
+
+