++ed by:

5 PAUSE users
7 non-PAUSE users.

Martin J Evans
and 2 contributors


DBD::ODBC::Changes - Log of significant changes to the DBD::ODBC

(As of $LastChangedDate: 2009-04-02 11:54:56 +0100 (Thu, 02 Apr 2009) $ $Revision: 10667 $)


 Add array parameter binding (per new DBI Spec)
 Add row caching/multiple row fetches to speed selects
 Better/more tests on multiple statement handles which ensure the
   correct number of rows
 Better/more tests on all queries which ensure the correct number of
   rows and data
 Better tests on SQLExecDirect/do
 Keep checking Oracle's ODBC drivers for Windows to fix the Date binding problem
 Change SQLSetConnectOption to SQLSetConnectAttr as we are ODBC 3 now
 Change SQLColAttributes calls (now deprecated) to SQLColAttribute
 Change SQLTransact calls to SQLEndTran calls.
 Add support for $sth->more_results based on DBD::ODBC-specific attribute
 Use odbcinst (if it exists to point people at the ini files they need to use)
 Use odbc_config (if it exists to find out about unixODBC).
 There is a Columns private ODBC method which is not documented.
 Add support for sending lobs in chunks instead of all in one go. Although
   DBD::ODBC uses SQLParamData and SQLPutData internally they are not exposed
   so anyone binding a lob has to have all of it available before it can
   be bound.
 Try to produce a Module::Install build.
 There is a blob_read method in DBI (undocumented) that DBD:DB2 & DBD::Pg
   use and might be useful in DBD::ODBC.
 The SQL_DRIVER_ODBC_VER attribute should be odbc_SQL_DRIVER_ODBC_VER.
 Why does level 15 tracing of any DBD::ODBC script show alot of these:
   !!DBD::ODBC unsupported attribute passed (PrintError)
   !!DBD::ODBC unsupported attribute passed (Username)
   !!DBD::ODBC unsupported attribute passed (dbi_connect_closure)
   !!DBD::ODBC unsupported attribute passed (LongReadLen)
  strawberry perl build issue:
  Add a perlcritic test - see DBD::Pg


Changes in DBD::ODBC 1.19 April 2, 2009

Some minor diagnostic output during tests when running against freeTDS to show we know of issues in freeTDS.

Fixed issue in 20SqlServer.t where the connection string got set with two consecutive semi-colons. Most drivers don't mind this but freeTDS ignores everything after that point in the connection string.

Quieten some delete table output during tests.

Handle connect failures in 20SqlServer.t in the multiple active statement tests.

In 02simple.t cope with ODBC drivers or databases that do not need a username or password (MS Access).

In 20SqlServer.t fix skip count and an erroneouse assignement for driver_name.

Changes some if tests to Test::More->is tests in 02simple.t.

Fix "invalid precision" error during tests with the new ACEODBC.DLL MS Access driver. Same workaround applied for the old MS Access driver (ODBCJT32.DLL) some time ago.

Fix out of memory error during tests against the new MS Access driver (ACEODBC.DLL). The problem appears to be that the new Access driver reports ridiculously large parameter sizes for "select ?" queries and there are some of these in the unicode round trip test.

Fixed minor typo in Makefile.PL - diagnostic message mentioned "ODBC HOME" instead of ODBCHOME.

12blob.t test somehow got lost from MANIFEST - replaced. Also changed algorithm to get a long char type column as some MS Access drivers only show SQL_WLONGVARCHAR type in unicode.

Added diagnostic output to 02simple.t to show the state of odbc_has_unicode.

Changes in DBD::ODBC 1.18_4 March 13, 2009

A mistake in the MANIFEST lead to the rt_43384.t test being omitted.

Brian Becker reported the tables PERL_DBD_39897 and PERL_DBD_TEST are left behind after testing. I've fixed the former but not the latter yet.

Yet another variation on the changes for rt 43384. If the parameter is bound specifically as SQL_VARCHAR, you got invalid precision error. Thanks to Øystein Torget for finding this and helping me verify the fix.

If you attempt to insert large amounts of data into MS Access (which does not have SQLDescribeParam) you can get an invalid precision error which can be worked around by setting the bind type to SQL_LONGVARCHAR. This version does that for you.

08bind2.t had a wrong skip count.

12blob.t had strict commented out and GetTypeInfo was not quoted. Also introduced a skip if the execute fails as it just leads to more obvious failures.

In dbdimp.c/rebind_ph there was a specific workaround for SQL Server which was not done after testing if we are using SQL Server - this was breaking tests to MS Access.

Changes in DBD::ODBC 1.18_2 March 9, 2009

Added yet another workaround for the SQL Server Native Client driver version 2007.100.1600.22 and 2005.90.1399.00 (driver version 09.00.1399) which leads to HY104, "Invalid precision value" in the rt_39841.t test.

Changes in DBD::ODBC 1.18_1 March 6, 2009

Fixed bug reported by Toni Salomäki leading to a describe failed error when calling procedures with no results. Test cases added to 20SqlServer.t.

Fixed bug rt 43384 reported by Øystein Torget where you cannot insert more than 127 characters into a Microsoft Access text(255) column when DBD::ODBC is built in unicode mode.

Changes in DBD::ODBC 1.18 January 16, 2009

Major release of all the 1.17 development releases below.

Changes in DBD::ODBC 1.17_3 December 19, 2008

Reinstated the answer in the FAQ for "Why do I get invalid value for cast specification" which had got lost - thanks to EvanCarroll in rt41663.

rt 41713. Applied patch from JHF Remmelzwaal to handle ODBC drivers which do not support SQL_COLUMN_DISPLAY_SIZE and SQL_COLUMN_LENGTH attributes in the SQLColAttributes calls after SQLTables and SQLColumns. Specifically, the driver he was using was the "Infor Integration ODBC driver".

Added notes from JHF Remmelzwaal on resolving some problems he came across building DBD::ODBC on Windows with Visual Studio 6.0 and SDK Feb 2003.

New odbc_column_display_size attribute for when drivers does not return a display size.

Loads of tracing changes to make it easier for me to debug problems.

Fixed bug in tracing of dbd_execute when parameter is char but undef which was leading to an access violation on Windows when tracing enabled.

Minor changes to diagnostic output in some rt tests.

One of the rt tests was not skipping the correct number of tests if the driver was not SQL Server.

Changes in DBD::ODBC 1.17_2 November 17, 2008

Changed ParamTypes attribute to be as specification i.e.,

    parameter_1 => {TYPE => sql_type}
    parameter_2 => {TYPE => sql_type}

and changed the tests in 07bind.t to reflect this.

A few minor perlcritic changes to ODBC.pm.

Added 99_yaml.t test to check META.yml.

Added patch from Spicy Jack to workaround problems with Strawberry Perl setting INC on the command line when running Makefile.PL.

Changes in DBD::ODBC 1.17_1 October 10, 2008

Missing newline from end of META.yml upsets cpan

Add code to Makefile.PL to spot command line containing INC, outline problem and resolution and not generate Makefile to avoid cpan-testers failures.

Loads of pod formatting changes including a section in the wrong place

New kwalitee test

Fix rt 39841. Bug in SQL Server ODBC driver which describes parameters by rearranging your SQL to do a select on the columns matching the parameters. Sometimes it gets this wrong and ends up describing the wrong column. This can lead to a varchar(10) being described with a column-size less than 10 and hence you get data truncation on execute.

Added a test case for rt 39841.

Fix rt 39897. 1.17 added support for varchar(max) in SQL Server but it broke support for SQL_VARCHAR columns in that they had LongReadLen and LongTruncOk applied to them. This means that in 1.16 you could retrieve a SQL_VARCHAR column without worrying about how long it was but in 1.17 if the same column was greater than 80 characters then you would get a truncated error. The only way the around this was to set LongTruncOk or LongReadLen.

Added a test case for rt 39897.

Changes in DBD::ODBC 1.17 September 22, 2008

In the absence of any bug reports since 1.16_4 this is the official 1.17 release. See below for changes since 1.16.

Minor pod changes.

Added support for ParamTypes (see DBI spec) and notes in DBD::ODBC pod.

Changes in DBD::ODBC 1.16_4 September 12, 2008

Small change to Makefile.PL to work around problem in darwin 8 with iODBC which leads to "Symbol not found: _SQLGetPrivateProfileString" errors.

Added new [n]varXXX(max) column type tests to 20SqlServer.t.

Fixed support for SQL_WCHAR and SQL_WVARCHAR support in non-unicode build. These types had ended up only being included for unicode builds.

More changes to ODBC pod to 1) encourage people to use CPAN::Reporter, 2) rework contributing section, 3) mention DBIx::Log4perl 4) add a BUGS section 5) add a "ODBC Support in ODBC Drivers" section etc.

Changed default fallback parameter bind type to SQL_WVARCHAR for unicode builds. This affects ODBC drivers which don't have SQLDescribeParam. Problem reported by Vasili Galka with MS Access when reading unicode data from one table and inserting it into another table. The read data was unicode but it was inserted as SQL_CHARs because SQLDescribeParam does not exist in MS Access so we fallback to either a default bind type (which was SQL_VARCHAR) or whatever was specified in the bind_param call.

Fixed bug in 20SqlServer.t when DBI_DSN is defined including "DSN=".

Changes in DBD::ODBC 1.16_3 September 3, 2008

Changed Makefile.PL to add "-framework CoreFoundation" to linker line on OSX/darwin.

Disallow building with iODBC if it is a unicode build.

More tracing for odbcconnect flag.

Fix bug in out connection string handling that attempted to use an out connection string when SQLDriverConnect[W] fails.

Fixed yet more test count problems due to Test::NoWarnings not being installed.

Skip private_attribute_info tests if DBI < 1.54

About a 30% rewrite of bound parameter code which started with an attempt to support the new VARBINARY(MAX) and VARCHAR(MAX) columns in SQL Server when the parameter length is > 400K in size (see elsewhere in this Changelog). This is a seriously big change to DBD::ODBC to attempt to be a bit more clever in its handling of drivers which either do not support SQLDescribeParam or do support SQLDescribeParam but cannot describe all parameters e.g., MS SQL Server ODBC driver cannot describe "select ?, LEN(?)". If you specify the bound parameter type in your calls to bind_param and run them to an ODBC driver which supports SQLDescribeParam you may want to check carefully and probably remove the parameter type from the bind_param method call.

Added rt_38977.t test to test suite to test varchar(max) and varbinary(max) columns in SQL Server.

Moved most of README.unicode to ODBC.pm pod.

Added workaround for problem with the Microsoft SQL Server driver when attempting to insert more than 400K into a varbinary(max) or varchar(max) column. Thanks to Julian Lishev for finding the problem and identifying 2 possible solutions.

Changes in DBD::ODBC 1.16_2 September 2, 2008

Removed szDummyBuffer field from imp_fbh_st and code in dbd_describe which clears it. It was never used so this was a waste of time.

Changed the remaining calls to SQLAllocEnv, SQLAllocConnect and SQLAllocStmt and their respective free calls to the ODBC 3.0 SQLAllocHandle and SQLFreeHandle equivalents.

Rewrote ColAttributes code to understand string and numeric attributes rather than trying to guess by what the driver returns. If you see any change in behaviour in ColAttributes calls you'll have to let me know as there were a number of undocumented workarounds for drivers.

Unicode build of DBD::ODBC now supports:

column names

The retrieval of unicode column names

SQL strings

Unicode in prepare strings (but not unicode parameter names) e.g.,

  select unicode_column from unicode_table

is fine but

  select * from table where column = :unicode_param_name

is not so stick to ascii parameter names if you use named parameters.

Unicode SQL strings passed to the do method are supported.

SQL strings passed to DBD::ODBC when the odbc_exec_direct attribute is set will not be passed as unicode strings - this is a limitation of the odbc_exec_direct attribute.

connection strings

True unicode connection string support will require a new version of DBI (post 1.607).

note that even though unicode connection strings are not supported currently DBD::ODBC has had to be changed to call SQLDriverConnectW/SQLConnectW to indicate to the driver manager it's intention to use some of the ODBC wide APIs. This only affects DBD::ODBC when built for unicode.

odbcunicode trace flag

There is a new odbcunicode trace flag to enable unicode-specific tracing.

Skipped 40Unicode.t test if the ODBC driver is Oracle's ODBC as I cannot make it work.

Changes internally to use sv_utf8_decode (where defined) instead of setting utf8 flag.

Fix problems in the test when Test::NoWarnings is not installed.

Removed some unused variables that were leading to compiler warnings.

Changed a lot of tracing to use new odbcconnection flag

Changed to use dbd_db_login6_sv if DBI supports it.

Commented out a diag in 20SqlServer.t that was leading to confusion.

Added diag to 20SqlServer.t in mars test to explain why it may fail.

Various pod changes for clarification and to note odbc_err_handler is deprecated.

Removed odbcdev trace flag - it was not really used.

New odbc_out_connect_string attribute for connections which returns the ODBC driver out connection string.

Changes in DBD::ODBC 1.16_1 August 28, 2008

Fixed bug in odbc_cancel which was checking the ACTIVE flag was on before calling SQLCancel. Non-select statements can also be cancelled so this was wrong. Thanks to Dean Arnold for spotting.

Minor changes to test 01base to attempt to catch install_driver failing, report it as a fail and skip other tests.

Fixed bug reported by James K. Lowden with asynchronous mode and SQLParamData where the code was not expecting SQL_STILL_EXECUTING and did not handle it

Added odbc_putdata_start attribute to determine when to start using SQLPutData on lobs.

Fixed bug in lob inserts where decimal_digits was being set to the size of the bound lob unnecessarily.

Minor change to connect/login code to delete driver-specific attributes passed to connect so they do not have to be processed again when DBI calls STORE with them.

New 12blob.t test.

A lot of code tidy up but not expecting any real benefit or detriment when using DBD::ODBC.

Fixed retrieving [n]varchar(max) columns which were only returning 1 byte - thanks to Fumiaki Yoshimatsu and perl monks for finding it. See http://markmail.org/message/fiym5r7q22oqlzsf#query:Fumiaki Yoshimatsu odbc+page:1+mid:fiym5r7q22oqlzsf+state:results

Various minor changes to get the CPANTS kwalitee score up. fixed pod issues in FAQ.pm moved mytest dir to examples added generated_by and requires perl version to META.yml added pod and pod-coverage tests removed executable flag from Makefile.PL added use warnings to some modules and tests fixed pod errors in ODBC.pm added AUTHOR and LICENSE section to ODBC.pm added Test::NoWarnings to tests

Added support for setting the new(ish) DBI ReadOnly attribute on a connection. See notes in pod.

Changes to test suite to work around problems in Oracle's instant client 11r1 ODBC driver for Linux (SQLColAttributes problems - see 02simple.t).

New tests in 30Oracle.t for oracle procedures.

Changes in DBD::ODBC 1.16 May 13, 2008

Test Changes

Small change to the last test in 10handler.t to cope with the prepare failing instead of the execute failing - spotted by Andrei Kovalevski with the ODBCng Postgres driver.

Changed the 20SqlServer.t test to specifically disable MARS for the test to check multiple active statements and added a new test to check that when MARS_Connection is enabled multiple active statements are allowed.

Changed the 09multi.t test to use ; as a SQL statement seperator instead of a newline.

A few minor "use of unitialised" fixes in tests when a test fails.

In 02simple.t Output DBMS_NAME/VER, DRIVER_NAME/VER as useful debugging aid when cpan testers report a fail.

2 new tests for odbc_query_timeout added to 03dbatt.t.

Changed 02simple.t test which did not work for Oracle due to a "select 1" in the test. Test changed to do "select 1 from dual" for Oracle.

New tests for numbered and named placeholders.

Documentation Changes

Added references to DBD::ODBC ohloh listing and markmail archives.

Added Tracing sections.

Added "Deviations from the DBI specification" section.

Moved the FAQ entries from ODBC.pm to new FAQ document. You can view the FAQ with perldoc DBD::ODBC::FAQ.

Added provisional README.windows document.

Rewrote pod for odbc_query_timeout.

Added a README.osx.

Internal Changes

More tracing in dbdimp.c for named parameters.

#ifdeffed out odbc_get_primary_keys in dbdimp.c as it is no longer used. $h->func($catalog, $schema, $table, 'GetPrimaryKeys') ends up in dbdimp.c/dbd_st_primary_keys now.

Reformatted dbdimp.c to avoid going over 80 columns.

Tracing changed. Levels reviewed and changed in many cases avoiding levels 1 and 2 which are reserved for DBI. Now using DBIc_TRACE macro internally. Also tracing SQL when 'SQL' flag set.

Build Changes

Changes to Makefile.PL to fix a newly introduced bug with 'tr', remove easysoft OOB detection and to try and use odbc_config and odbcinst if we find them to aid automatic configuration. This latter change also adds "odbc_config --cflags" to the CC line when building DBD::ODBC.

Avoid warning when testing ExtUtils::MakeMaker version and it is a test release with an underscore in the version.

Functionality Changes

Added support for parse_trace_flag and parse_trace_flags methods and defined a DBD::ODBC private flag 'odbcdev' as a test case.

Add support for the 'SQL' trace type. Added private trace type odbcdev as an experimental start.

Change odbc_query_timeout attribute handling so if it is set to 0 after having set it to a non-zero value the default of no time out is restored.

Added support for DBI's statistics_info method.

Bug Fixes

Fix bug in support for named placeholders leading to error "Can't rebind placeholder" when there is more than one named placeholder.

Guard against scripts attempting to use a named placeholder more than once in a single SQL statement.

If you called some methods after disconnecting (e.g., prepare/do and any of the DBD::ODBC specific methods via "func") then no error was generated.

Fixed issue with use of true/false as fields names in structure on MAC OS X 10.5 (Leopard) thanks to Hayden Stainsby.

Remove tracing of bound wide characters as it relies on null-terminated strings that don't exist.

Fix issue causing a problem with repeatedly executing a stored procedure which returns no result-set. SQLMoreResults was only called on the first execute and some drivers (SQL Server) insist a procedure is not finished until SQLMoreResults returns SQL_NO_DATA.

Changes in DBD::ODBC 1.15 January 29, 2008

1.15 final release.

Fixed bug reported by Toni Salomaki where DBD::ODBC may call SQLNumResultCols after SQLMoreResults returns SQL_NO_DATA. It led to the error:

Describe failed during DBI::st=HASH(0x19c2048)->FETCH(NUM_OF_FIELDS,0)

when NUM_OF_FIELDS was referenced in the Perl script.

Updated odbc_exec_direct documentation to describe its requirement when creating temporary objects in SQL Server.

Added FAQ on SQL Server temporary tables.

Fixed bug in dbdimp.c which was using SQL_WCHAR without testing it was defined - thanks Jergen Dutch.

Fixed use of "our" in UCHelp.pm which fails on older Perls.

Minor changes to 02simple.t and 03dbatt.t to fix diagnostics output and help debug DBD which does not handle long data properly.

Further changes to Makefile.PL to avoid change in behavior of ExtUtils::MakeMaker wrt order of execution of PREREQ_PM and CONFIGURE. Now if DBI::DBD is not installed we just warn and exit 0 to avoid a cpan-testers failure.

Changes in DBD::ODBC 1.15_2 November 14, 2007

Fix bug in DBD::ODBC's private function data_sources which was returning data sources prefixed with "DBI:ODBC" instead of "dbi:ODBC".

If you don't have at least DBI 1.21 it is now a fatal error instead of just a warning.

DBI->connect changed so informational diagnostics like "Changed database context to 'master'" from SQL Server are available in errstr/state. These don't cause DBI->connect to die but you can test $h->err eq "" after connect and obtain the informational diagnostics from errstr/state if you want them.

Fixed problem in 41Unicode.t where utf8 was used before testing we had a recent enough Perl - thank you cpan testers.

Changed "our" back to "my" in Makefile.PL - thank you cpan testers.

Removed all calls to DBIh_EVENT2 in dbdimp.c as it is no longer used (see posts on dbi-dev).

Changed text output when a driver manager is not found to stop referring to iodbcsrc which is no longer included with DBD::ODBC.

Changed Makefile.PL to attempt to find unixODBC if -o or ODBCHOME not specified.

Updated META.yml based on new 1.2 spec.

Changed Makefile.PL so if an ODBC driver manager is not found then we issue warning and exit cleanly but not generating a Makefile. This should stop cpan-testers from flagging a fail because they haven't got an ODBC driver manager.

Changed Makefile.PL so it no longer "use"s DBI/DBI::DBD because this makes cpan-testers log a fail if DBI is not installed. Changed to put the DBI::DBD use in the CONFIGURE sub so PREREQ_PM will filter out machines where DBI is not installed.

Fix a possible typo, used once in 10handler.t.

Changes in DBD::ODBC 1.15_1 November 6, 2007

Minor changes to 20SqlServer.t test for SQL Server 2008 (Katmai). Timestamps now return an extra 4 digits of precision (all 0000) and the driver reported in dbcc messages has a '.' in the version which was not handled.

New FAQ entry and test code for "Datetime field overflow" problem in Oracle.

Changed all ODBC code to use new SQLLEN/SQLULEN types where Microsoft's headers indicate, principally so DBD::ODBC builds and works on win64. NOTE: you will need an ODBC Driver Manager on UNIX which knows SQLLEN/SQLULEN types. The unixODBC driver manager uses SQLLEN/SQLULEN in versions from at least 2.2.12. Thanks to Nelson Oliveira for finding, patching and testing this and then fixing problems with bound parameters on 64 bit Windows.

Added private_attribute_info method DBI introduced (see DBI docs) and test cases to 02simple.t.

Fairly major changes to dbd_describe in dbdimp.c to reduce ODBC calls by 1 SQLDescribeCol call per column when describing result sets. Instead of calculating the amount of memory required to hold every column name we work on the basis that (num_columns + 1) * SQL_MAX_COLUMN_NAME_LEN can hold all column names. However, to avoid using a large amount of memory unnecessarily if an ODBC driver supports massive column name lengths the maximum size per column is restricted to 256.

Changed to avoid using explicit use of DBIc_ERRXXX in favour of newish (ok, DBD::ODBC is a bit behind the times in this respect) DBIh_SET_ERR_CHAR. This involved a reworking or the error handling and although all test cases still pass I cannot guarantee it has no other effects - please let me know if you spot differences in error messages.

Fixed bug in 20SqlServer test for multiple results that was passing but for the wrong reason (namely, that the odbc_err_handler was being called when it should not have been).

Fixed bug in odbc_err_handler that prevented it from being reset so you don't have an error handler. Looks like the problem was in dbd_db_STORE_attrib where "if(valuesv == &PL_sv_undef)" was used to detect undef and I think it should be "if (!SvOK(valuesv))".

Improvements to odbc_err_handler documentation.

Added 10handler.t test cases.

More tests in 02simple.t to check NUM_OF_FIELDS and NAMES_uc.

Bit of a tidy up:

Removed some unused variable declarations from dbdimp.c.

Lots of changes to DBD::ODBC tracing, particularly in dbd_describe, and dbd_error2 and login6.

Removed a lot of tracing code in comments or #if 0 as it never gets built.


Changes in DBD::ODBC 1.14 July 17, 2007

Fix bug reported where ping crashes after disconnect thanks to Steffen Goeldner.

Fix bug in dbd_bind_ph which leads to the error Can't change param 1 maxlen (51->50) after first bind in the 20SqlServer test. This is caused by svGROW in Perl 5.8.8 being changed to possibly grow by more than you asked (e.g. up to the next longword boundary).

Fix problem with binding undef as an output parameter. Reported by Stephen More with IBM's ODBC driver for iSeries.

Removed comment delimiters in comments in dbdimp.h leading to warnings.

Removed some unused variable declarations leading to warnings.

Removed PerlIO_flush calls as it is believed they are not required.

Add logging for whether SQLDescribeParam is supported.

Fixed use of unitialised variable in dbd_bind_ph where an undef is bound and tracing is enabled.

Fixed issue with TRACESTATUS change in 20SqlServer.t tests 28, 31, 32 and 33 leading to those tests failing when testing with SQL Server 2005 or Express.

Many compiler warnings fixed - especially for incompatible types.

Add provisional Unicode support - thanks to Alexander Foken. This change is very experimental (especially on UNIX). Please see ODBC.pm documentation. Also see README.unicode and README.af. New database attribute odbc_has_unicode to test if DBD::ODBC was built with UNICODE support. New tests for Unicode. New requirement for Perl 5.8.1 if Unicode support required. New -[no]u argument to Makefile.PL. New warning in Makefile.PL if Unicode support built for UNIX.

Fix use of unitialised var in Makefile.PL.

Fix use of scalar with no effect on Makefile.PL

Added warning to Makefile.PL about building/running with LANG using UTF8.

Added warning to Makefile.PL about using thread-safe ODBC drivers.

Updated MANIFEST to include more test code from mytest and remove MANIFEST.SKIP etc.

Removed calls to get ODBC errors when SQLMoreResults returns SQL_NO_DATA. These are a waste of time since SQL_NO_DATA is expected and there is no error diagnostic to retrieve.

Changes to test 17 of 02simple.t which got "not ok 17 - Col count matches correct col count" errors with some Postgres ODBC drivers. Caused by test expecting column names to come back uppercase. Fixes by uppercasing returned column names.

Changes to tests in 03batt.t which correctly expects an ODBC 3 driver to return the column names in SQLTables result-set as per ODBC 3.0 spec. Postgres which reports itself as an ODBC 3.0 driver seems to return the ODBC 2 defined column names. Changed tests to catch ODBC 2.0 names are pass test put issue warning.

For postgres skip test (with warning) checking $sth->{NAME} returns empty listafter execute on update

Updated FAQ, added a few more questions etc.

DBD::ODBC requires at least 5.6.0 of Perl.

Many updates to pod documentation.

Removed some dead HTTP links in the pod I could not find equivalents for - let me know if you have working replacements for ones removed

Add some HTTP links to useful tutorials on DBD::ODBC

Changes in DBD::ODBC 1.13 November 8, 2004

Fix inconsistency/bug with odbc_exec_direct vs. odbc_execdirect settings. Now made consistent with odbc_exec_direct. For now, will still look for odbc_execdirect in prepare, but not as DBH attribute as a backup (which is what it was doing), but that support will be dropped at some time in the future. Please use odbc_exec_direct from now on...

Fix handling of print statements for SQL Server thanks to Martin Evans! Thanks for all your work on this! Due to bug in SQL Server, you must use odbc_exec_direct. See t/20SqlServer.t for example. You will need to call $sth->{odbc_more_results} to clear out any trailing messages.

Change tests to use Test::More. Whew, that's much nicer!

Fix Oracle integral/numeric output params so that warning not printed about value not being numeric (even though it is!)

Changes in DBD::ODBC 1.12 October 26, 2004

Fix bug with odbc_execdirect attributed thanks to Martin Evans Fix bug(s) with odbc_query_timeout and tested with SQL*Server. Oracle tests failed with setting timeout. Probably not handled by Oracle's ODBC driver

Changes in DBD::ODBC 1.11 October 11, 2004

Added odbc_timeout, but untested

Changes in DBD::ODBC 1.10 September 8, 2004

Fixed bug in Makefile.PL. Added pod.t test, taken from DBI. Fixed various small POD issues, discovered during the pod test. Fixed bug in bind_param_inout

Changes in DBD::ODBC 1.09 March 10, 2004

Duh. I forgot to add new dbivport.h to MANIFEST and SVN before submitting. Fixed.

Changes in DBD::ODBC 1.08 March 6, 2004

Added check in Makefile.PL to detect if the environment variable LANG is Set. If so, prints a warning about potential makefile generation issues. Change to use dbivport.h per new DBI spec. Add ability to set the cursor type during the connect. This may allow some servers which do not support multiple concurrent statements to permit them -- tested with SQL Server. Thanks to Martin Busik! See odbc_cursortype information in the ODBC POD.

Changes in DBD::ODBC 1.07 February 19, 2004

Added to Subversion version control hosted by perl.org. Thanks Robert! See ODBC.pm POD for more information. Added contributing section to ODBC.pm POD -- see more details there! Added parameter to odbc_errhandler for the NativeError -- thanks to Martin Busik. Fix for Makefile.PL not having tab in front of $(NOOP) (Finally). Fix for SQLForeignKeys thanks to Kevin Shepherd.

Changes in DBD::ODBC 1.06 June 19, 2003

Fixed test in t/02simple.t to skip if the DSN defined by the user has DSN= in it. Added tests for wrong DSN, ensuring the DBI::errstr is appropriately set. Fixed small issue in Makefile.PL for Unix systems thanks to H.Merijn Brand. Update to NOT copy user id and password to connect string if UID or PWD parameter in connect string. Updated Makefile.PL for dmake, per patch by Steffen Goldner. Thanks Steffen!

Changes in DBD::ODBC 1.05 March 14, 2003

Cleaned up Makefile.PL and added Informix support thanks to Jonathan Leffler (see README.informix) Added nicer error message when attempting to do anything while the database is disconnected. Fixed fetchrow_hashref('NAME_uc | NAME_lc') with odbc_more_results. Added exporter to allow perl -MDBD::ODBC=9999 command line to determine version Fixed for building with DBI 1.33 and greater Removed all C++ style comments Ensured files are in Unix format, with the exception of the README type information and Makefile.PL

Changes in DBD::ODBC 1.04 January 24, 2003

It seems that case insensitive string comparison with a limit causes problems for multiple platforms. strncmpi, strncasecmp, _strcmpin are all functions hit and it seems to be a hit-or-miss. Hence, I rewrote it to upper case the string then do strncmp, which should be safe...sheesh. A simple thing turned into a headache...

Changes in DBD::ODBC 1.03 January 17, 2003

Add automatic detection of DRIVER= or DSN= to add user id and password to connect string.

Changes in DBD::ODBC 1.02 January 6, 2003

Fix to call finish() automatically if execute is re-called in a loop (and test in t/02simple.t to ensure it's fixed)

Augmented error message when longs are truncated to help users determine where to look for help.

Fixes for build under Win32 with Perl5.8.

Changes in DBD::ODBC 1.01 December 9, 2002

Forgot to fix require DBI 1.201 in ODBC.pm to work for perl 5.8. Fixed

Changes in DBD::ODBC 1.00 December 8, 2002

(Please see all changes since version 0.43)

Updated Makefile.PL to handle SQL_Wxxx types correctly with unixODBC and linking directly with EasySoft OOB. Note that I could not find where iODBC defines SQL_WLONG_VARCHAR, so I'm not sure it's fixed on all other platforms. Should not have been a problem under Win32...

Found that the fix in _18 was only enabled if debug enabled and it broke something else. removed the fix.

Updated Makefile.PL to use DBI version 1.21 instead of 1.201 to facilitate builds under latest development versions of Perl.

Updated code to use the *greater* of the column display size and the column length for allocating column buffers. This *should* workaround a problem with DBD::ODBC and the Universe database.

Added code thanks to Michael Riber to handle SQLExecDirect instead of SQLPrepare. There are two ways to get this:

        $dbh->prepare($sql, { odbc_execdirect => 1});
        $dbh->{odbc_execdirect} = 1;

When $dbh->prepare() is called with the attribute "ExecDirect" set to a non-zero value dbd_st_prepare do NOT call SQLPrepare, but set the sth flag odbc_exec_direct to 1.

Fixed numeric value binding when binding non-integral values. Now lets the driver or the database handle the conversion.

Fixed makefile.pl generation of makefile to force the ODBC directory first in the include list to help those installing ODBC driver managers on systems which already have ODBC drivers in their standard include path.

Changes in DBD::ODBC 0.45_18 September 26, 2002

Updated MANIFEST to include more of the mytest/* files (examples, tests) Fixed problem when attempting to get NUM_OF_FIELDS after execute returns no rows/columns.

Changes in DBD::ODBC 0.45_17 August 26, 2002

More fixes for multiple result sets. Needed to clear the DBIc_FIELDS_AV when re-executing the multiple-result set stored procedure/query.

Changes in DBD::ODBC 0.45_16 August 26, 2002

Updated to fix output parameters with multiple result sets. The output parameters are not set until the last result set has been retrieved.

Changes in DBD::ODBC 0.45_15 August 20, 2002

Updated for new DBIc_STATE macros (all debug, as it turned out) to be thread safer in the long run

Updated for the new DBIc_LOGFP macros

Added CLONE method

Fix for SQL Server where multiple result sets being returned from a stored proc, where one of the result sets was empty (insert/update).

Added new attribute odbc_force_rebind, which forces DBD::ODBC to check recheck for new result sets every execute. This is only really necessary if you have a stored procedure which returns different result sets with each execute, given the same "prepare". Many times this will be automatically set by DBD::ODBC, however, if there is only one result set in the stored proc, but it can differ with each call, then DBD::ODBC will not know to set it.

Updated the DBD::ODBC POD documentation to document DBD::ODBC private attributes and usage.

Changes in DBD::ODBC 0.45_14 August 13, 2002

Added support to handle (better) DBI begin_work().

Fix for binding undef parameters on SQL Server.

Fix bug when connecting twice in the same script. Trying to set the environment ODBC version twice against the same henv caused an error.

Changes in DBD::ODBC 0.45_13 August 9, 2002

Workaround problem with iODBC where SQLAllocHandleStd is not present in iODBC. Made Changes file accessible via perldoc DBD::ODBC::Changes. In the near future the change log will be removed from here and put in changes to tidy up a bit.

Changes in DBD::ODBC 0.45_12 August 9, 2002

Fixed global destruction access violation (which was seemingly random).

Changes in DBD::ODBC 0.45_11 August 8, 2002

Updated manifest to include more samples. Working on checking for leaks on Linux, where I might get more information about the process memory.

Working on fixing problems with MS SQL Server binding parameters. It seems that SQLServer gets "confused" if you bind a NULL first. In "older" (SQLServer 2000 initial release) versions of the driver, it would truncate char fields. In "newer" versions of the SQL Server driver, it seems to only truncate dates (actually, round them to the nearest minute). If you have problems in the SQL Server tests, please upgrade your driver to the latest version on Microsoft's website (MDAC 2.7 or above) http://www.microsoft.com/data

Changes in DBD::ODBC 0.45_10 July 30, 2002

Added database specific tests to ensure things are working. Some of the tests may not work for all people or may not be desirable. I have tried to keep them as safe as possible, but if they don't work, please let me know.

Added support for the internal function GetFunctions to handle ODBC 3's SQL_API_ODBC3_ALL_FUNCTIONS. Would have caused a memory overwrite on the stack if it was called.

Changes in DBD::ODBC 0.45_9 July 30, 2002

Fixed bug in procedure handling for SQLServer. Was not re-describing the result sets if the SQLMoreResults in the execute needs to be called.

Changes in DBD::ODBC 0.45_8 July 25, 2002

Fixed bug in tracing code when binding an undef parameter which did not happen to have a valid buffer with tracing level >= 2

Fixed bug when binding undef after a valid data bind on a timestamp. The Scale value was being calculated based upon the string that had been bound prior to the bind of the undef and if that had a sub-second value, then the scale would be set to the wrong value...I.e.

 bind_param(1, '2000-05-17 00:01:00.250', SQL_TYPE_TIMESTAMP) then
 bind_param(1, undef, SQL_TYPE_TIMESTAMP) then

Fixed SQL Server issue when binding a null and the length was set to 0 instead of 1

Changes in DBD::ODBC 0.45_7 July 25, 2002

Adding support for array binding, but not finished.

Fixed bug where SqlServer Stored procedures which perform INSERT would not correctly return a result set. Thanks to Joe Tebelskis for finding it and Martin Evans for supplying a fix.

Fixed bug where binding the empty string would cuase a problem. Fixed and added test in t/07bind.t.

Changes in DBD::ODBC 0.45_6 July 24, 2002

Added support for new DBI ParamValues feature.

Changes in DBD::ODBC 0.45_5 July 23, 2002

Added odbc_err_handler and odbc_async_exec thanks to patches by David L. Good. See example in mytest/testerrhandler.pl

Here's the notes about it:

 I've implemented two separate functions.  The first is an "error
 handler" similar to that in DBD::Sybase.  The error handler can be used
 to intercept error and status messages from the server.  It is the only
 way (at least currently) that you can retrieve non-error status messages
 when execution is successful.

 To use the error handler, set the "odbc_err_handler" attribute on
 your database handle to a reference to a subroutine that will act
 as the error handler.  This subroutine will be passed two args, the
 SQLSTATE and the error message.  If the subroutine returns 0, the
 error message will be otherwise ignored.  If it returns non-zero,
 the error message will be processed normally.

 The second function implemented is asynchronous execution.  It's only
 useful for retrieving server messages with an error handler during an
 execute() that takes a long time (such as a DBCC on a large database) ODBC
 doesn't have the concept of a callback routine like Sybase's DBlib/CTlib
 does, so asynchronous execution is needed to be able to get the server
 messages before the SQL statement is done processing.

 To use asynchronous execution, set the "odbc_async_exec" attribute on
 your database handle to 1.  Not all ODBC drivers support asynchronous
 execution.  To see if yours does, set odbc_async_exec to 1 and then check
 it's value.  If the value is 1, your ODBC driver can do asynchronous
 execution.  If the value is 0, your ODBC driver cannot.

Changes in DBD::ODBC 0.45_4 July 22, 2002

More fixes for DB2 tests and timestamp handling.

Changes in DBD::ODBC 0.45_3 July 22, 2002

Changes to internal timestamp type handling and test structure to ensure tests work for all platforms. DB2 was giving me fits due to bad assumptions. Thanks to Martin Evans (again) for help in identifying the problems and helping research solutions. This includes the scale/precision values to correctly store full timestamps.

Changes in DBD::ODBC 0.45_2 July 19, 2002

Moving API usage to ODBC 3.0 specifications. With lots of help from Martin Evans (again!). Thanks Martin!!!!!

Changes in DBD::ODBC 0.44 July 18, 2002

.44 was never officially released. Fix for do() and execute to handle DB2 correctly. Patch/discovery thanks to Martin Evans. Partly moving towards defaulting to ODBC 3.x standards.

Changes in DBD::ODBC 0.43 July 18, 2002

Fix for FoxPro (and potentially other) Drivers!!!!!

Add support for DBI column_info

Fix for binding undef value which comes from dereferencing hash

Fix to make all bound columns word (int) aligned in the buffer.

Changes in DBD::ODBC 0.42 July 8, 2002

Added patches to the tests to support ActiveState's automated build process.

Fix ping() to try SQLTables for a test, instead of a strange query.

Changes in DBD::ODBC 0.41 April 15, 2002

Fixed problem where SQLDescribeParam would fail (probably bug in ODBC driver). Now reverts to SQL_VARCHAR if that happens, instead of failing the query.

Fixed error report when using Oracle's driver. There is a known problem. Left the error on the test, but added warning indicating it's a known problem.

Changes in DBD::ODBC 0.40 April 12, 2002

Most significant change is the change in the default binding type which forces DBD::ODBC to attempt to determine the bind type if one is not passed. I decided to make this the default behavior to make things as simple as possible.

Fixed connection code put in 0.39 to work correctly.

Two minor patches for building, one for Cygwin one if both iODBC and unixODBC libraries are installed. Probably need better command line on this, but if someone has the problem, please let me know (and hopefully send a patch with it).

Changes in DBD::ODBC 0.39 March 12, 2002

See mytest/longbin.pl for demonstration of inserting and retrieving long binary files to/from the db. Uses MD5 algorithm to verify data. Please do some similar test(s) with your database before using it in production. The various bind types are different for each database!

Finally removed distribution of old iODBC. See www.iodbc.org or www.unixodbc.org for newer/better versions of the ODBC driver manager for Unix (and others?).

Added ability to force ODBC environment version.

Fix to SQLColAttributes.

Changes to connect sequence to provide better error messages for those using DSN-less connections.

Changes in DBD::ODBC 0.38 February 12, 2002

Fixed do function (again) thanks to work by Martin Evans.

Changes in DBD::ODBC 0.37 February 10, 2002

Patches for get_info where return type is string. Patches thanks to Steffen Goldner. Thanks Steffen!

Patched get_info to NOT attempt to get data for SQL_DRIVER_HSTMT and SQL_DRIVER_HDESC as they expect data in and have limited value (IMHO).

Further fixed build for ODBC 2.x drivers. The new SQLExecDirect code had SQLAllocHandle which is a 3.x function, not a 2.x function. Sigh. I should have caught that the first time. Signed, the Mad-and- not-thorough-enough-patcher.

Additionally, a random core dump occurred in the tests, based upon the new SQLExecDirect code. This has been fixed.

Changes in DBD::ODBC 0.36 February 10, 2002

Fixed build for ODBC 2.x drivers. The new SQLExecDirect code had SQLFreeHandle which is a 3.x function, not a 2.x function.

Changes in DBD::ODBC 0.35 February 9, 2002

Fixed (finally) multiple result sets with differing numbers of columns. The final fix was to call SQLFreeStmt(SQL_UNBIND) before repreparing the statement for the next query.

Added more to the multi-statement tests to ensure the data retrieved was what was expected.

Now, DBD::ODBC overrides DBI's do to call SQLExecDirect for simple statements (those without parameters). Please advise if you run into problems. Hopefully, this will provide some small speed improvement for simple "do" statements. You can also call $dbh->func($stmt, ExecDirect). I'm not sure this has great value unless you need to ensure SQLExecDirect is being called. Patches thanks to Merijn Broeren. Thanks Merijn!

Changes in DBD::ODBC 0.34 February 7, 2002

Further revamped tests to attempt to determine if SQLDescribeParam will work to handle the binding types. The t/08bind.t attempts to determine if SQLDescribeParam is supported. note that Oracle's ODBC driver under NT doesn't work correctly when binding dates using the ODBC date formatting {d } or {ts }. So, test #3 will fail in t/08bind.t

New support for primary_key_info thanks to patches by Martin Evans. New support for catalog, schema, table and table_type in table_info thanks to Martin Evans. Thanks Martin for your work and your continuing testing, suggestions and general support!

Support for upcoming dbi get_info.

Changes in DBD::ODBC 0.33_3 February 4, 2002

Revamped tests to include tests for multiple result sets. The tests are ODBC driver platform specific and will be skipped for drivers which do not support multiple result sets.

Changes in DBD::ODBC 0.33_2 February 4, 2002

Finally tested new binding techniques with SQL Server 2000, but there is a nice little bug in their MDAC and ODBC drivers according to the knowledge base article # Q273813, titled

   "FIX: "Incorrect Syntax near the Keyword 'by' "
   Error Message with Column Names of "C", "CA" or "CAS" (Q273813)

DBD::ODBC now does not name any of the columns A, B, C, or D they are now COL_A, COL_B, COL_C, COL_D.

 BINDING the default for future versions.  I do not believe
 it will break much existing code (if any) as anyone binding
 to non VARCHAR (without the ODBC driver doing a good conversion
 from the VARCHAR) will have a problem.  It may be subtle, however,
 since much code will work, but say, binding dates may not with
 some drivers.

 Please comment soon...

Changes in DBD::ODBC 0.33_1 February 4, 2002

*** WARNING: ***

 Changes to the binding code to allow the use of SQLDescribeParam
 to determine if the type of column being bound.  This is
 experimental and activated by setting

  $dbh->{odbc_default_bind_type} = 0; # before creating the query...

Currently the default value of odbc_default_bind_type = SQL_VARCHAR which mimicks the current behavior. If you set odbc_default_bind_type to 0, then SQLDescribeParam will be called to determine the columen type. Not ALL databases handle this correctly. For example, Oracle returns SQL_VARCHAR for all types and attempts to convert to the correct type for us. However, if you use the ODBC escaped date/time format such as: {ts '1998-05-13 00:01:00'} then Oracle complains. If you bind this with a SQL_TIMESTAMP type, however, Oracle's ODBC driver will parse the time/date correctly. Use at your own risk!

Fix to dbdimp.c to allow quoted identifiers to begin/end with either " or '. The following will not be treated as if they have a bind placeholder:

   '01-JAN-1987 00:00:00'
   'Does anyone insert a ?'

Changes in DBD::ODBC 0.32 January 22, 2002

More SAP patches to Makfile.PL to eliminate the call to Data Sources

A patch to the test (for SAP and potentially others), to allow fallback to SQL_TYPE_DATE in the tests

Changes in DBD::ODBC 0.31 January 18, 2002

Added SAP patches to build directly against SAP driver instead of driver manager thanks to Flemming Frandsen (thanks!)

Added support to fix ping for Oracle8. May break other databases, so please report this as soon as possible. The downside is that we need to actually execute the dummy query.

Changes in DBD::ODBC 0.30 January 8, 2002

Added ping patch for Solid courtesy of Marko Asplund

Updated disconnect to rollback if autocommit is not on. This should silence some errors when disconnecting.

Updated SQL_ROWSET_SIZE attribute. Needed to force it to odbc_SQL_ROWSET_SIZE to obey the DBI rules.

Added odbc_SQL_DRIVER_ODBC_VER, which obtains the version of the Driver upon connect. This internal capture of the version is a read-only attributed and is used during array binding of parameters.

Added odbc_ignore_named_placeholders attribute to facilicate creating triggers within SAPDB and Oracle, to name two. The syntax in these DBs is to allow use of :old and :new to access column values before and after updates. Example:

 $dbh->{odbc_ignore_named_placeholders} = 1; # set it for all future statements
                                          # ignores :foo, :new, etc, but not :1 or ?
 $dbh->do("create or replace etc :new.D = sysdate etc");

Changes in DBD::ODBC 0.29 August 22, 2001

Cygwin patches from Neil Lunn (untested by me). Thanks Neil!

SQL_ROWSET_SIZE attribute patch from Andrew Brown

 There are only 2 additional lines allowing for the setting of
 SQL_ROWSET_SIZE as db handle option.

 The purpose to my madness is simple. SqlServer (7 anyway) by default
 supports only one select statement at once (using std ODBC cursors).
 According to the SqlServer documentation you can alter the default setting
 three values to force the use of server cursors - in which case multiple
 selects are possible.

 The code change allows for:
 $dbh->{SQL_ROWSET_SIZE} = 2;    # Any value > 1

 For this very purpose.

 The setting of SQL_ROWSET_SIZE only affects the extended fetch command as
 far as I can work out and thus setting this option shouldn't affect
 DBD::ODBC operations directly in any way.


VMS and other patches from Martin Evans (thanks!)

[1] a fix for Makefile.PL to build DBD::ODBC on OpenVMS.

[2] fix trace message coredumping after SQLDriverConnect

[3] fix call to SQLCancel which fails to pass the statement handle properly.

[4] consume diagnostics after SQLDriverConnect/SQLConnect call or they remain until the next error occurs and it then looks confusing (this is due to ODBC spec for SQLError). e.g. test 02simple returns a data truncated error only now instead of all the informational diags that are left from the connect call, like the "database changed", "language changed" messages you get from MS SQL Server.

Replaced C++ style comments with C style to support more platforms more easily.

Fixed bug which use the single quote (') instead of a double quote (") for "literal" column names. This helped when having a colon (:) in the column name.

Fixed bug which would cause DBD::ODBC to core-dump (crash) if DBI tracing level was greater than 3.

Fixed problem where ODBC.pm would have "use of uninitialized variable" if calling DBI's type_info.

Fixed problem where ODBC.xs *may* have an overrun when calling SQLDataSources.

Fixed problem with DBI 1.14, where fprintf was being called instead of PerlIO_printf for debug information

Fixed problem building with unixODBC per patch from Nick Gorham

Added ability to bind_param_inout() via patches from Jeremy Cooper. Haven't figured out a good, non-db specific way to test. My current test platform attempts to determine the connected database type via ugly hacks and will test, if it thinks it can. Feel free to patch and send me something...Also, my current Oracle ODBC driver fails miserably and dies.

Updated t/02simple.t to not print an error, when there is not one.

Changes in DBD::ODBC 0.28 March 23, 2000

Added support for SQLSpecialColumns thanks to patch provided by Martin J. Evans [martin@easysoft.com]

Fixed bug introduced in 0.26 which was introduced of SQLMoreResults was not supported by the driver.

Changes in DBD::ODBC 0.27 March 8, 2000

Examined patch for ping method to repair problem reported by Chris Bezil. Thanks Chris!

Added simple test for ping method working which should identify this in the future.

Changes in DBD::ODBC 0.26 March 5, 2000

Put in patch for returning only positive rowcounts from dbd_st_execute. The original patch was submitted by Jon Smirl and put back in by David Good. Reasoning seems sound, so I put it back in. However, any databases that return negative rowcounts for specific reasons, will no longer do so.

Put in David Good's patch for multiple result sets. Thanks David! See mytest\moreresults.pl for an example of usage.

Added readme.txt in iodbcsrc explaining an issue there with iODBC 2.50.3 and data_sources.

Put in rudimentary cancel support via SQLCancel. Call $sth->cencel to utilize. However, it is largely untested by me, as I do not have a good sample for this yet. It may come in handy with threaded perl, someday or it may work in a signal handler.

Changes in DBD::ODBC 0.25 March 4, 2000

Added conditional compilation for SQL_WVARCHAR and SQL_WLONGVARCHAR. If they are not defined by your driver manager, they will not be compiled in to the code. If you would like to support these types on some platforms, you may be able to #define SQL_WVARCHAR (-9) #define SQL_WLONGVARCHAR (-10)

Added more long tests with binding in t\09bind.t. Note use of bind_param!

Changes in DBD::ODBC 0.24 February 24, 2000

Fixed Test #13 in 02simple.t. Would fail, improperly, if there was only one data source defined.

Fixed (hopefully) SQL Server 7 and ntext type "Out of Memory!" errors via patch from Thomas Lowery. Thanks Thomas!

Added more support for Solid to handle the fact that it does not support data_sources nor SQLDriverConnect. Patch supplied by Samuli Karkkainen [skarkkai@woods.iki.fi]. Thanks! It's untested by me, however.

Added some information from Adam Curtin about a bug in iodbc 2.50.3's data_sources. See iodbcsrc\readme.txt.

Added information in this pod from Stephen Arehart regarding DSNLess connections.

Added fix for sp_prepare/sp_execute bug reported by Paul G. Weiss.

Added some code for handling a hint on disconnect where the user gets an error for not committing.

Changes in DBD::ODBC 0.22 September 8, 1999

Fixed for threaded perl builds. Note that this was tested only on Win32, with no threads in use and using DBI 1.13. Note, for ActiveState/PERL_OBJECT builds, DBI 1.13_01 is required as of 9/8/99. If you are using ActiveState's perl, this can be installed by using PPM.

Changes in DBD::ODBC 0.21

Thanks to all who provided patches!

Added ability to connect to an ODBC source without prior creation of DSN. See mytest/contest.pl for example with MS Access. (Also note that you will need documentation for your ODBC driver -- which, sadly, can be difficult to find).

Fixed case sensitivity in tests.

Hopefully fixed test #4 in t/09bind.t. Updated it to insert the date column and updated it to find the right type of the column. However, it doesn't seem to work on my Linux test machine, using the OpenLink drivers with MS-SQL Server (6.5). It complains about binding the date time. The same test works under Win32 with SQL Server 6.5, Oracle 8.0.3 and MS Access 97 ODBC drivers. Hmmph.

Fixed some binary type issues (patches from Jon Smirl)

Added SQLStatistics, SQLForeignKeys, SQLPrimaryKeys (patches from Jon Smirl) Thanks (again), Jon, for providing the build_results function to help reduce duplicate code!

Worked on LongTruncOk for Openlink drivers.

Note: those trying to bind variables need to remember that you should use the following syntax:

        use DBI;
        $sth->bind_param(1, $str, DBI::SQL_LONGVARCHAR);

Added support for unixodbc (per Nick Gorham) Added support for OpenLinks udbc (per Patrick van Kleef) Added Support for esodbc (per Martin Evans) Added Support for Easysoft (per Bob Kline)

Changed table_info to produce a list of views, too. Fixed bug in SQLColumns call. Fixed blob handling via patches from Jochen Wiedmann. Added data_sources capability via snarfing code from DBD::Adabas (Jochen Wiedmann)

Changes in DBD::ODBC 0.20 August 14, 1998

SQLColAttributes fixes for SQL Server and MySQL. Fixed tables method by renaming to new table_info method. Added new tyoe_info_all method. Improved Makefile.PL support for Adabase.

Changes in DBD::ODBC 0.19

Added iODBC source code to distribution.Fall-back to using iODBC header files in some cases.

Changes in DBD::ODBC 0.18

Enhancements to build process. Better handling of errors in error handling code.

Changes in DBD::ODBC 0.17

This release is mostly due to the good work of Jeff Urlwin. My eternal thanks to you Jeff.

Fixed "SQLNumResultCols err" on joins and 'order by' with some drivers (see Microsoft Knowledge Base article #Q124899). Thanks to Paul O'Fallon for that one.

Added more (probably incomplete) support for unix ODBC in Makefile.PL

Increased default SQL_COLUMN_DISPLAY_SIZE and SQL_COLUMN_LENGTH to 2000 for drivers that don't provide a way to query them dynamically. Was 100!

When fetch reaches the end-of-data it automatically frees the internal ODBC statement handle and marks the DBI statement handle as inactive (thus an explicit 'finish' is *not* required).


LongTruncOk for Oracle ODBC (where fbh->datalen < 0)

Added tracing into SQLBindParameter (help diagnose oracle odbc bug)

Fixed/worked around bug/result from Latest Oracle ODBC driver where in SQLColAttribute cbInfoValue was changed to 0 to indicate fDesc had a value

Added work around for compiling w/ActiveState PRK (PERL_OBJECT)

Updated tests to include date insert and type

Added more "backup" SQL_xxx types for tests

Updated bind test to test binding select

 NOTE: bind insert fails on Paradox driver (don't know why)

Added support for: (see notes below)

  SQLGetInfo       via $dbh->func(xxx, GetInfo)
  SQLGetTypeInfo   via $dbh->func(xxx, GetTypeInfo)
  SQLDescribeCol   via $sth->func(colno, DescribeCol)
  SQLColAttributes via $sth->func(xxx, colno, ColAttributes)
  SQLGetFunctions  via $dbh->func(xxx, GetFunctions)
  SQLColumns       via $dbh->func(catalog, schema, table, column, 'columns')

Fixed $DBI::err to reflect the real ODBC error code which is a 5 char code, not necessarily numeric.

Fixed fetches when LongTruncOk == 1.

Updated tests to pass more often (hopefully 100% <G>)

Updated tests to test long reading, inserting and the LongTruncOk attribute.

Updated tests to be less driver specific.

They now rely upon SQLGetTypeInfo heavily in order to create the tables. The test use this function to "ask" the driver for the name of the SQL type to correctly create long, varchar, etc types. For example, in Oracle the SQL_VARCHAR type is VARCHAR2, while MS Access uses TEXT for the SQL Name. Again, in Oracle the SQL_LONGVARCHAR is LONG, while in Access it's MEMO. The tests currently handle this correctly (at least with Access and Oracle, MS SQL server will be tested also).

1 POD Error

The following errors were encountered while parsing the POD:

Around line 97:

Non-ASCII character seen before =encoding in 'Øystein'. Assuming UTF-8