ID: 16244 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: No Feedback Bug Type: Sybase (dblib) related Operating System: Redhat Linux 7.2 PHP Version: 4.1.2 New Comment:
No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. Previous Comments: ------------------------------------------------------------------------ [2002-11-06 09:54:47] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip ------------------------------------------------------------------------ [2002-06-10 04:26:54] [EMAIL PROTECTED] In fact php make a mistake on the length of the text buffer vs the number of characters. In a unicode string there are 2 bytes per characters. PHP thinks that the number is the number of characters... For instance the SQL network dump show the record as: 00d1 0400 "A"00 "R"00 and php takes 0400 as the number of characters instead of the number of bytes and then report: "AR " instead of "AR" It is to be expected that this bug is on all unicode types... I use MS-SQL7.0 freetds0.53 snapshot the sybase-php code (not sybase-ct) and on Mandrake 8.2. ------------------------------------------------------------------------ [2002-03-24 10:52:10] [EMAIL PROTECTED] When accessing a Microsoft SQL Server 2000 database using the sybase access libraries and FreeTDS 0.53 running in TDS 7.0 mode, fields of type 'nvarchar' do not appear the same as they do in the database. Usually there are trailing characters from previous rows which have already been fetched, pointing to a null-terminator/string length issue. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=16244&edit=1
