aboutsummaryrefslogblamecommitdiffstats
path: root/lib/odbc/doc/src/notes.xml
blob: 1f9b3b4290cc2655fbd659979e0d8856803439c3 (plain) (tree)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
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>