6
I Use This!
Very Low Activity

News

Analyzed 1 day ago. based on code collected 1 day ago.
Posted about 5 years ago by martinjevans
I just released the 3rd development release of DBD::ODBC (1.39_3). Apart from a few bug fixes and other changes (see below) this release adds support for MS SQL Server Query Notification. Query notification allows an application to request a ... [More] notification from SQL Server when the results of a query change. Once set up you can block on an execute call waiting for the query to change. Here is an excerpt from the pod: MS SQL Server Query Notification read more [Less]
Posted about 5 years ago by martinjevans
I just released the 3rd development release of DBD::ODBC (1.39_3). Apart from a few bug fixes and other changes (see below) this release adds support for MS SQL Server Query Notification. Query notification allows an application to request a ... [More] notification from SQL Server when the results of a query change. Once set up you can block on an execute call waiting for the query to change. Here is an excerpt from the pod: MS SQL Server Query Notification read more [Less]
Posted over 5 years ago by martinjevans
I have just uploaded DBD::ODBC 1.47 to the CPAN. This release does contain significant changes in behaviour for unicode builds of DBD::ODBC so I hope when I warned you months ago you tested it. Thanks to everyone on the dbi-dev list and irc that ... [More] helped me work my way through the unicode issue. I'm now going to sit back and wait for the usual rush of reports from everyone who didn't test it. See below for changes since last full release. 1.47 2014-02-19 Full release of the 1.46 development releases. [MISCELLANEOUS] read more [Less]
Posted over 5 years ago by martinjevans
I have just uploaded DBD::ODBC 1.47 to the CPAN. This release does contain significant changes in behaviour for unicode builds of DBD::ODBC so I hope when I warned you months ago you tested it. Thanks to everyone on the dbi-dev list and irc that ... [More] helped me work my way through the unicode issue. I'm now going to sit back and wait for the usual rush of reports from everyone who didn't test it. See below for changes since last full release. 1.47 2014-02-19 Full release of the 1.46 development releases. [MISCELLANEOUS] read more [Less]
Posted over 5 years ago by martinjevans
I've just uploaded DBD::ODBC 1.46_2 to the CPAN. In the process of writing Some Common Unicode Problems and Solutions using Perl DBD::ODBC and MS SQL Server and github repo I discovered a serious bug in the way DBD::ODBC can attempt to insert unicode ... [More] characters into char/varchar/longvarchar columns. This experimental release fixes that issue but it does mean this release contains a significant change in behaviour. Since 1.46_1 yet another unicode fix was added too. read more [Less]
Posted over 5 years ago by martinjevans
I've just uploaded DBD::ODBC 1.46_2 to the CPAN. In the process of writing Some Common Unicode Problems and Solutions using Perl DBD::ODBC and MS SQL Server and github repo I discovered a serious bug in the way DBD::ODBC can attempt to insert unicode ... [More] characters into char/varchar/longvarchar columns. This experimental release fixes that issue but it does mean this release contains a significant change in behaviour. Since 1.46_1 yet another unicode fix was added too. read more [Less]
Posted over 5 years ago by martinjevans
I've just uploaded DBD::ODBC 1.46_1 to the CPAN. In the process of writing Some Common Unicode Problems and Solutions using Perl DBD::ODBC and MS SQL Server and github repo I discovered a serious bug in the way DBD::ODBC can attempt to insert unicode ... [More] characters into char/varchar/longvarchar columns. This experimental release fixes that issue but it does mean this release contains a significant change in behaviour. read more [Less]
Posted over 5 years ago by martinjevans
I've just uploaded DBD::ODBC 1.46_1 to the CPAN. In the process of writing Some Common Unicode Problems and Solutions using Perl DBD::ODBC and MS SQL Server and github repo I discovered a serious bug in the way DBD::ODBC can attempt to insert unicode ... [More] characters into char/varchar/longvarchar columns. This experimental release fixes that issue but it does mean this release contains a significant change in behaviour. read more [Less]
Posted over 5 years ago by martinjevans
As promised a few days ago, I've now uploaded an official release of the DBD::ODBC 1.44 development series to the CPAN as 1.45. Whilst writing Unicode support via Perl DBD::ODBC and MS SQL Server - common problems I came across a serious unicode bug ... [More] in DBD::ODBC which affects inserts into char/varchar columns. After much discussion on dbi-dev I am now embarking on a fix and the current progress (which is functional now) can be found at varchar_unicode_insert branch. If you use DBD::ODBC you are strongly advised to try it out (even now). I am hoping to release this as a development release soon to allow more people to easily test it. read more [Less]
Posted over 5 years ago by martinjevans
I've just uploaded DBD::ODBC 1.45 to the CPAN. As always I'd draw your attention to a few small changes in behaviour. The changes since 1.43 are listed below but I need to warn you about an upcoming change first. WARNING - PLEASE READ: ===== The next ... [More] development cycle of DBD::ODBC will contain signficant changes to the way unicode strings in your Perl scripts are inserted into CHAR and VARCHAR columns. In an attempt to write up exactly how this all works (see https://github.com/mjegh/dbd_odbc_sql_server_unicode and http://www.mail-archive.com/dbi-dev@perl.org/msg07364.html) I have discovered that unicode strings are not being inserted into CHAR/VARCHAR columns correctly in the unicode build of DBD::ODBC. There may also be changes to how unicode strings are read back from the database but I have not evaluated that yet. Please make sure you keep an eye out of DBD::ODBC development releases 1.46_N and ensure you test them before the next full release is made. In the mean time if you are using unicode with DBD::ODBC and have any comments, have hit any strange issues or are using any workarounds I strongly urge you to contact me now before I get too far into these changes. ===== read more [Less]