2.19 Bug Fixes
Fixed incorrect handling of various "new" datatypes (date,
time, bigint, bigdatetime).
Other Bug Fixes:
640 - Sybase::BLK fails due to system table ordering issues
consequence of row level locking on system tables in
15.0.2 and later.
2.18 Bug Fixes
Various BLK fixes.
Fixed Sybase::BCP and Sybase::BLK tests which failed against
12.5.3 servers (changes on the Server side).
Bugs Fixed:
577 - perl Makefile.PL fails if umask is 0.
2.17 Kerberos Network login
Support for CS_SEC_NETWORKAUTH and CS_SEC_SERVERPRINCIPAL
connection properties in Sybase::CTlib.
Support CS_SERVERADDR connection properties in Sybase::CTlib,
and also allow the $server parameter to ct_connect to be
specified as "host:port" (requires OpenClient 12.5.1 or later).
Some documentation changes/improvements in Sybase::CTlib.
Bug Fixes
546 umask checking doesn't work on Windows.
555 blk_rowxfer doesn't handle datatype conversion errors.
560 Long binary columns are truncated by ct_fetch.
542 Fetch binary in raw format.
538 DBlib doesn't export TRACE_xxx symbols.
Problems found with existing distfiles:
distfiles/D6.data.ros.gz
distfiles/cstore0.2.tar.gz
distfiles/data4.tar.gz
distfiles/sphinx-2.2.7-release.tar.gz
No changes made to the cstore or mariadb55-client distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
sybperl includes four modules: Sybase::DBlib, Sybase::CTlib,
Sybase::BCP and Sybase::Sybperl. The first two implement a thin
wrapper around the Sybase DB-Library and Client Library APIs,
respectively. Sybase::BCP is a specialty module aimed at doing
Bulk-Copy operations, and Sybase::Sybperl is a compatibility module
with sybperl 1.xx (i.e. with the perl 4.x version).
The sybperl modules are thin wrappers around the Sybase APIs. This is
both good and bad. It's good because you have greater control, and
because the API is (obviously) close to the way the server and the
protocol work. It's bad in that it's a proprietary API, and that it is
somewhat verbose.
