ID: 27279
Updated by: [EMAIL PROTECTED]
Reported By: webmaster at birkman dot com
-Status: Open
+Status: Bogus
Bug Type: Sybase (dblib) related
Operating System: Linux 2.4 to MSSQL2000
PHP Version: 4.3.4
New Comment:
Please don't open this anymore, search again.
Previous Comments:
[2004-02-18 08:16:25] webmaster at birkman dot com
Changed status to open
[2004-02-17 08:46:07] webmaster at birkman dot com
I searched on various keywords (whitespace, sybase, spacing, extra
spaces) and nothing came up related to this issue of 4.3.2 -> 4.3.4
spacing. If you wouldn't mind, could you please post links to the bugs
you're referencing, and I'll be more than happy to move my comments?
Also, I have CLI versions of 4.3.2 and 4.3.4 both built with the exact
same libraries showing the bug. And I have a 4.3.4 version built (exact
same way) except the 'if ilia_0' has been commented out of
php_sybase_db.c, and it works fine.
[2004-02-16 11:05:15] [EMAIL PROTECTED]
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same.
Thank you for your interest in PHP.
This is due to a bug in the library not PHP. For more
information search for similar bugs (there were several).
[2004-02-16 09:40:22] webmaster at birkman dot com
Description:
In looking at the ChangeLog, I don't see anything describing the
behavior I'm seeing. Most of the data returned from the database has
whitespace at the end, even bits and integers.
Has something changed requiring the use of trim() on every resultset
coming from a sybase database? Wouldn't a trim() operation in C be
faster than one in PHP?
This behavior occurs in PHP-4.3.4 but not in our production version of
PHP-4.3.2
Thanks,
David Steckbeck
--
Edit this bug report at http://bugs.php.net/?id=27279&edit=1
