| 1 |
libdbd-odbc-perl (1.50-1) unstable; urgency=medium |
| 2 |
|
| 3 |
NOTES from upstream Changes file: |
| 4 |
|
| 5 |
[CHANGE IN BEHAVIOUR] |
| 6 |
|
| 7 |
* As warned years ago, this release removes the odbc_old_unicode attribute. |
| 8 |
|
| 9 |
* As warned years ago, the private data_sources method has been removed - |
| 10 |
use DBI one instead. |
| 11 |
|
| 12 |
-- gregor herrmann <[email protected]> Sat, 26 Jul 2014 13:43:17 +0200 |
| 13 |
|
| 14 |
libdbd-odbc-perl (1.48-1) unstable; urgency=medium |
| 15 |
|
| 16 |
NOTES from upstream Changes file: |
| 17 |
|
| 18 |
[CHANGE IN BEHAVIOUR] |
| 19 |
|
| 20 |
* As warned in release 1.45, the binding of unicode parameters to |
| 21 |
char/varchar columns has changed significantly. If you don't attempt |
| 22 |
to insert unicode into char/varchar columns or if you only inserted |
| 23 |
unicode into nchar/nvarchar columns you should see no difference. |
| 24 |
From this release, unicode data inserted into |
| 25 |
char/varchar/longvarchar columns is bound as SQL_WCHAR and not |
| 26 |
whatever the driver reports the parameter as (which is mostly |
| 27 |
SQL_CHAR). |
| 28 |
|
| 29 |
* Previously if DBD::ODBC received an error or (SQL_SUCCESS_WITH_INFO) |
| 30 |
from an ODBC API call and then the driver refused to return the |
| 31 |
error state/text DBD::ODBC would issue its own error saying "Unable |
| 32 |
to fetch information about the error" and state IM008. That state |
| 33 |
was wrong and has been changed to HY000. |
| 34 |
|
| 35 |
-- Xavier Guimard <[email protected]> Fri, 21 Mar 2014 06:29:40 +0100 |
| 36 |
|
| 37 |
libdbd-odbc-perl (1.43-1) unstable; urgency=low |
| 38 |
|
| 39 |
NOTES from upstream Changes file: |
| 40 |
|
| 41 |
[CHANGE IN BEHAVIOUR] |
| 42 |
|
| 43 |
* As I warned literally years ago DBD::ODBC's private function |
| 44 |
DescribeCol has been removed. You can use DBI's statement attributes |
| 45 |
like NAME, PRECISION etc, instead. All test code has been changed to |
| 46 |
remove calls to DescribeCol and GetTypeInfo. |
| 47 |
|
| 48 |
* DBD::ODBC allowed you to change the bound column type in bind_col |
| 49 |
after the column was already bound. It now does not allow this |
| 50 |
and issues a warning. |
| 51 |
|
| 52 |
* You can nolonger override the bound column type (except with |
| 53 |
SQL_NUMERIC and SQL_DOUBLE). All columns are now bound as either |
| 54 |
SQL_C_LONG (integer columns) or SQL_C_[W]CHAR (all other columns). |
| 55 |
If you are calling bind_col with a TYPE => xxx it most likely did |
| 56 |
not do what you expected and you should examine it carefully with a |
| 57 |
view to removing it altogether. As a result you no longer have to |
| 58 |
override the bind type for MS SQL Server XML columns - these will be |
| 59 |
bound as SQL_C_CHAR or SQL_C_WCHAR depending on whether Unicode is |
| 60 |
enabled. |
| 61 |
|
| 62 |
* Integer columns are now bound as SQL_C_LONGs and not as before, |
| 63 |
SQL_C_CHAR. This should not matter to you but if you were adding 0 |
| 64 |
to your integer columns retrieved to make them behave like integers |
| 65 |
you should nolonger need to do it. |
| 66 |
|
| 67 |
-- Xavier Guimard <[email protected]> Tue, 30 Oct 2012 07:24:10 +0100 |
| 68 |
|
| 69 |
libdbd-odbc-perl (1.37-1) unstable; urgency=low |
| 70 |
|
| 71 |
NOTES from upstream Changes file: |
| 72 |
|
| 73 |
[CHANGE IN BEHAVIOUR] |
| 74 |
|
| 75 |
* The odbc_disable_array_operations has been replaced with |
| 76 |
odbc_array_operations and the default for array operations is off. |
| 77 |
Sorry, but I warned this was experimental. The |
| 78 |
ODBC_DISABLE_ARRAY_OPERATIONS env var remains. |
| 79 |
|
| 80 |
* In execute_for_fetch set the parameter status array to all 9999 |
| 81 |
(which is invalid) so we can see if the ODBC driver actually sets |
| 82 |
them and we can warn if they don't. |
| 83 |
|
| 84 |
* For freeTDS default odbc_disable_array_operations to 1 as no |
| 85 |
version of the freeTDS driver can be found that works. I was |
| 86 |
requested to do this by the dbix-class guys. I may revert this |
| 87 |
later if freeTDS is fixed. |
| 88 |
|
| 89 |
* as above for MS Access. It is a shame I cannot find any way of |
| 90 |
finding out if a driver is capable of array operations. |
| 91 |
|
| 92 |
-- gregor herrmann <[email protected]> Tue, 10 Apr 2012 19:44:26 +0200 |
| 93 |
|
| 94 |
libdbd-odbc-perl (1.35-1) unstable; urgency=low |
| 95 |
|
| 96 |
NOTE from upstream Changes file: |
| 97 |
|
| 98 |
Prior to this release if you called selectall_* methods with a |
| 99 |
non-select statement DBD::ODBC would raise an error saying "no |
| 100 |
select statement currently executing". See RT 68720. After |
| 101 |
discussions on dbi-dev the concensus seems to be that issuing a |
| 102 |
warning in this case is better so that is what I've done. As a |
| 103 |
result t/rt_68720.t has been removed and |
| 104 |
t/85_selectall_non_select.t has been added. |
| 105 |
|
| 106 |
-- gregor herrmann <[email protected]> Sun, 18 Mar 2012 18:36:09 +0100 |
| 107 |
|
| 108 |
libdbd-odbc-perl (1.29-1) unstable; urgency=low |
| 109 |
|
| 110 |
NOTE from upstream Changes file: |
| 111 |
|
| 112 |
The 1.28 development releases made a change which causes a generic |
| 113 |
error to be reported when an ODBC call fails but an error message |
| 114 |
is not retrieved from the ODBC Driver. It appears this has caught |
| 115 |
out a few ODBC drivers - notably freeTDS and Firebird. You now may |
| 116 |
see errors that were missed before e.g., DBIx::Class's tests for |
| 117 |
Firebird now errors test 21 "outer txn rolled back" (and others) |
| 118 |
because SQLRowCount returns an error after "ROLLBACK TO SAVEPOINT |
| 119 |
savepoint_0"; before this error was missed. |
| 120 |
|
| 121 |
-- gregor herrmann <[email protected]> Wed, 09 Mar 2011 17:34:36 +0100 |
| 122 |
|
| 123 |
libdbd-odbc-perl (1.27-1) unstable; urgency=low |
| 124 |
|
| 125 |
This release marks a change where DBD::ODBC has now gone entirely |
| 126 |
ODBC 3, and relies on the ODBC Driver Manager to map calls to |
| 127 |
ODBC 2 drivers. This change may break applications relying on the |
| 128 |
former ODBC 2 functionality. |
| 129 |
|
| 130 |
-- Jonathan Yu <[email protected]> Mon, 21 Feb 2011 10:09:35 -0500 |