#14397 [Com]: Wrong results when reading a float

From: Date: Thu, 13 Mar 2003 10:40:20 +0000
Subject: #14397 [Com]: Wrong results when reading a float
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-35498@lists.php.net to get a copy of this message
ID: 14397 Comment by: gwenzel at emb dot de Reported By: hofmann at isl dot org Status: No Feedback Bug Type: Sybase (dblib) related Operating System: Linux PHP Version: 4.0.6 New Comment: I Experienced the same problem, but found a workaround. If I enclose the offending column by CAST(clumn AS DECIMAL) I get the correct result. Previous Comments: ------------------------------------------------------------------------ [2002-09-10 12:45:17] kinkie at tiscalinet dot it I have verified the same problem. In a table stored on a mssql 6.5 server, accessed via FreeTDS (both release 0.53 and 0.60.rc3) I have a column which is a float(24). I can confirm that accessing that table works fine both from the tsql utility supplied with freetds and from sqsh. That column's fields are however zeroed out when I access from inside PHP. This is both on 4.1.1 and 4.2.2. The host operating system is Redhat 7.1. ------------------------------------------------------------------------ [2002-03-18 05:20:33] tony at ec-server dot com I have the same error with PHP4.1.1. Even though I use float(16) instead of float(8), or use decimal(15,5), I got the wrong display when fetch a float/decimal/double field. ------------------------------------------------------------------------ [2002-01-28 10:41:54] sander@php.net No feedback. ------------------------------------------------------------------------ [2002-01-07 02:35:05] lobbin@php.net Can you reproduce this error with PHP 4.1.1? ------------------------------------------------------------------------ [2001-12-10 02:36:19] hofmann at isl dot org I found that the wrong float results happen with float(8) but NOT with float(16) !!! ------------------------------------------------------------------------ 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/14397 -- Edit this bug report at http://bugs.php.net/?id=14397&edit=1

« previous php.bugs (#35498) next »