Hi to both internals lists,

> Admittedly, it is only an issue for Microsoft SQL Server (mssql and
> pdo_mssql) and for Sybase_ct.

How about Sybase-CT, does this happen also with PDO and Sybase DBLIB? If not
using FreeTDS, both 3rd party DLLs are legacy non-VC9 libs/dlls
(libsybct.dll, libsybdb.dll as of Sybase 15). Is this the problem or
something other?

In general (this is why I also write to the internals list): DBLIB is no
longer supported by Sybase, CT is preferred, according to Sybase. Only with
FreeTDS, DBLIB *was* more bugfree, because simplier code (this is no longer
true). There is only one problem, the name of lib and dll changed in Sybase
Open Client 15, from libct to libsybct (and so on for the other files, to
fix the problem with another non-sybase libct on some UNIXes), so configure
should check this.

In my opinion, Sybase CT should be fixed and the old DBLIB extension
dropped. On the other hand, I also use PDO-ODBC with the Sybase ODBC /
FreeTDS ODBC drivers, so this is currently my preferred configuration (on
unix). The Sybase PDO driver is also "not the right way" according to
Sybase, because it uses DBLIB. And it does not support prepared statements
directly and correctly escaping quotes in the workaround. CTLIB supports
prepared statements, DBLIB not (because to old and no longer supported).

Uwe


-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to