#23316 [Opn->Bgs]: Loss of precision in float data when SQL Server is queried
| From: | fmk@php.net | Date: | Tue, 20 May 2003 23:42:38 +0000 |
| Subject: | #23316 [Opn->Bgs]: Loss of precision in float data when SQL Server is queried | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-40101@lists.php.net to get a copy of this message | ||
ID: 23316
Updated by: fmk@php.net
Reported By: hammer88 at hotmail dot com
-Status: Open
+Status: Bogus
Bug Type: MSSQL related
Operating System: Windows 2000
PHP Version: 4.3.2-RC
New Comment:
MSSQL server will return 2 digits after the decimal point for money and
small money solumns.
You can use the convert() function to increase this to 4 digits.
Previous Comments:
------------------------------------------------------------------------
[2003-05-20 18:21:59] fmk@php.net
updating php.exe and php4ts.dll is not enough. all the mssql functions
are located in php_mssql.dll.
------------------------------------------------------------------------
[2003-04-30 19:39:30] hammer88 at hotmail dot com
I did not try modifying the locale format. My solution was just
modifying the data type in SQL Server so it was a decimal instead of
money. All is well.
------------------------------------------------------------------------
[2003-04-30 06:14:45] sniper@php.net
Did changing the currency settings affect this or not?
------------------------------------------------------------------------
[2003-04-24 03:26:49] sniper@php.net
try it?
------------------------------------------------------------------------
[2003-04-23 16:20:30] hammer88 at hotmail dot com
Replaced the php.exe & php4ts.dll files and verified the new version
with phpinfo(). But problem still persisted. Is this because php
utilizes the local computer's currency settings? Which I assume
default for Windows is two decimal places? That wouldn't be cool to
have to change that default just for this instance... ideas?
------------------------------------------------------------------------
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/23316
--
Edit this bug report at http://bugs.php.net/?id=23316&edit=1