-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi debian folk.
> It's possible that the problem is also specific to tables containing > non-ASCII data. You mentioned that the problem was not reproducible > for you when using sqsh; could you also provide a sample result set > for a query that succeeds with sqsh and fails with php5-sybase? I don't think it's the same bug, but it's really close. Please take a look at this one: http://bugs.php.net/bug.php?id=33693 If also concerns sybase-ct and iconv. See this sample script connecting to a MS SQL server: <?php putenv('TDSVER=7.0'); $db = sybase_connect($server, $username, $password); sybase_select_db('MODULES', $db); sybase_query("DROP TABLE test_tbl"); sybase_query("CREATE TABLE test_tbl (a INT, b NVARCHAR(255), c UNIQUEIDENTIFIER)"); sybase_query("INSERT INTO test_tbl VALUES (1, N'Hello World', NEWID())"); if (($q1 = sybase_query("SELECT a, b FROM test_tbl"))) print_r(sybase_fetch_row($q1)); if (($q2 = sybase_query("SELECT a, b, c FROM test_tbl"))) print_r(sybase_fetch_row($q2)); ?> This outputs: Array ( [0] => 1 [1] => Hello World ) error_handler: Data-conversion resulted in overflow. Segmentation fault If you replace the TDSVER=7.0 with TDSVER=4.2 you get: Array ( [0] => 1 [1] => Hello World ) Array ( [0] => 1 [1] => Hello World [2] => 244ebbc892d6f24694ab8a08836fa86d ) Obviously it would be better if this is fixed upstream. But this bug has existed since 2005 and for me personally I only need it fixed in Debian and Ubuntu ;-) Regards, Walter Doekes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG/iRcHeLk+LNJZ18RAnUpAKC9VUo8SPsVd+S0S08dSzGg2O9SZgCgp5Yr tTYtwWKyCMYzzHjUYk4tP9M= =skrN -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
