#20641 [Fbk->Opn]: Numeric type returns invalid result using ibase_fetch_row/ibase_fetch_object

ID: 20641 User updated by: jear at aabc dot dk Reported By: jear at aabc dot dk -Status: Feedback +Status: Open Bug Type: InterBase related Operating System: Windows NT / Firebird 1.0 PHP Version: 4.2.3 New Comment: I've downloaded og installed the latest STABLE snaphot with ALL the dlls. After rebooting, the same erroneous number is returned from Interbase to PHP: IB/Firebird datatype (decimal 10,0), value 2303511415 returns 2147483647. Previous Comments: ------------------------------------------------------------------------ [2003-03-31 03:33:38] sniper@php.net Make sure that you REALLY updated to the latest STABLE snaphot and ALL the dlls. (and you might need to reboot even) (don't install anything when your webserver is running) ------------------------------------------------------------------------ [2003-03-31 03:08:09] jear at aabc dot dk I've tried current CVS and php_4_3 for Windows. Unfortunately the numeric/decimal datatype beyond the bounds of the PHP integer type (> 2147483647), still causes an overflow. Example: InterBase 2303511415 (decimal 10,0) returns 2147483647 ------------------------------------------------------------------------ [2003-03-13 16:13:10] daniela@php.net Fixed in current CVS and php_4_3 ------------------------------------------------------------------------ [2003-02-11 02:37:53] jear at aabc dot dk I've tried the CVS snapshot for Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip Unfortunately the numeric/decimal datatype beyond the bounds of the PHP integer type (> 2147483647), still causes an overflow. integer overflow is still there. ------------------------------------------------------------------------ [2003-02-10 13:01:59] iliaa@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/20641 -- Edit this bug report at http://bugs.php.net/?id=20641&edit=1