From freddy77 at gmail.com Sun May 16 06:34:36 2021 From: freddy77 at gmail.com (Frediano Ziglio) Date: Sun, 16 May 2021 11:34:36 +0100 Subject: [freetds] FreeTDS 1.3 Release Candidate 1 Message-ID: Hi, time for a new release! Although the stable branch is kept updated with bugs and minor features, new big features, build improvements and potential compatibility changes are not ported to the stable branch. The reasons for a new release are UTF-8 support for MSSQL 2019 and the removal of the obsolete (and wrong) "8.0" version which won't be recognized anymore. Here (available also in NEWS file) changes for next release: Summary of Changes in release 1.3 -------------------------------------------- User visible (not in a particular order): - Generic: - Support UTF-8 columns using MSSQL 2019; - Do not accept TDS protocol versions "4.6" (never really supported) and "8.0"; - Minor portability issues; - Fix log elision for login; - Detect some possible minor memory failure in application; - Support long (more than 64k) SSPI packets (never encountered but you never know); - Fix unicode columns for ASA database; - Avoid using BCP with old protocols; - (*) Fix bulk copy using big endian machines; - (*) Fix Sybase uni(var)char and unsigned types for big endian machines; - (*) Do not send nullable data during bulk copy if type is not nullable; - ODBC: - Added "Timeout" setting; - Applications: - Improve defncopy utility: - Fix some declaration; - Fix Sybase support; - (*) Fix datacopy and freebcp logging; - CT-Library: - Minor fix for variant type; - Better support for timeout setting; - (*) Support some missing types (like nullable unsigned integers) for Sybase; - DB-library: - Unify date format (all systems can use the same syntax); - (*) Allows to pass 0 as type for bcp_bind; - (*) Fix DBSETLSERVERPRINCIPAL macro; - (*) Do not limit queries length for bcp using Sybase; - (*) Add KEEP_NULLS to BCP hints. (*) Feature backported in stable 1.2 branch. Implementation: - Move replacement headers under freetds directory for coherence with other internal headers; - Lots of style updates; - Optimize UTF-8 encoding for ODBC, reuse common code. Kind Regards, Frediano From freddy77 at gmail.com Fri Jun 4 08:35:22 2021 From: freddy77 at gmail.com (Frediano Ziglio) Date: Fri, 4 Jun 2021 13:35:22 +0100 Subject: [freetds] FreeTDS 1.3 Release Candidate 2 Message-ID: FreeTDS 1.3 Release Candidate 2 Hi, another updated release candidate. I expect this is the last release candidate, there were just some minor updates: - Fixed some issue with OpenVMS; - Updated Userguide. Release changes for next release (available also in NEWS file): Summary of Changes in release 1.3 -------------------------------------------- User visible (not in a particular order): - Generic: - Support UTF-8 columns using MSSQL 2019; - Do not accept TDS protocol versions "4.6" (never really supported) and "8.0"; - Minor portability issues; - Fix log elision for login; - Detect some possible minor memory failure in application; - Support long (more than 64k) SSPI packets (never encountered but you never know); - Fix unicode columns for ASA database; - Avoid using BCP with old protocols; - (*) Fix bulk copy using big endian machines; - (*) Fix Sybase uni(var)char and unsigned types for big endian machines; - (*) Do not send nullable data during bulk copy if type is not nullable; - ODBC: - Added "Timeout" setting; - Applications: - Improve defncopy utility: - Fix some declaration; - Fix Sybase support; - (*) Fix datacopy and freebcp logging; - CT-Library: - Minor fix for variant type; - Better support for timeout setting; - (*) Support some missing types (like nullable unsigned integers) for Sybase; - DB-library: - Unify date format (all systems can use the same syntax); - (*) Allows to pass 0 as type for bcp_bind; - (*) Fix DBSETLSERVERPRINCIPAL macro; - (*) Do not limit queries length for bcp using Sybase; - (*) Add KEEP_NULLS to BCP hints. (*) Feature backported in stable 1.2 branch. Implementation: - Move replacement headers under freetds directory for coherence with other internal headers; - Lots of style updates; - Optimize UTF-8 encoding for ODBC, reuse common code. Kind Regards, Frediano