ezfloat - rounding up number issue

Previous topic

Developer

Next topic

Author	Message
steve walker	Friday 27 July 2007 6:35:53 am Hi there, We have an issue with ezfloat in conjunction the l10n operator. It seems its covered to an extent here: http://issues.ez.no/3755 However, I havent been abl to fix our issue - which is that we are storing financial figures in a system - and when the numbers start going over 1,000,000 the number start getting rounded to the nearest 100. The full operator is: \|l10n(number) How can I change the operator so that it just displays the exact number without any rounding, preferably with 2 decimal places? Many thanks, Steve. http://www.oneworldmarket.co.uk
Felipe Jaramillo	Wednesday 01 August 2007 10:15:03 am Hi Steve, We have now reproduced, investigated and solved the rounding issue. It is related to the default mysql database structure, where numbers (float) are 4 bytes and rounded after 6 figures by default. We have successfully changed this to allow 15 figure numbers before rounding them. After doing the change in our test servers, it does not disrupt the existing data. In my opinion, people should be warned about this inaccuracy as it affects any default installation and there is no alternative datatype for accurately storing long numbers other than TextLine. This inaccuracy is present in the existing numbers 6 figure numbers and up as they are rounded. Eg. 1234567 is stored as 1234570. To fix: Increase length of FLOAT to 25 (8 bytes) in “data_float” field in table “ezcontentobject_attribute”, which will effectively make it a DOUBLE 8byte number, accurate to 15 figure numbers. More info in: http://dev.mysql.com/doc/refman/4.1/en/choosing-types.html http://dev.mysql.com/doc/refman/4.1/en/storage-requirements.html http://dev.mysql.com/doc/refman/4.1/en/numeric-types.html Felipe Jaramillo eZ Certified Extension Developer http://www.aplyca.com \| Bogotá, Colombia

Author

Message

steve walker

Friday 27 July 2007 6:35:53 am

Hi there,

We have an issue with ezfloat in conjunction the l10n operator. It seems its covered to an extent here:

http://issues.ez.no/3755

However, I havent been abl to fix our issue - which is that we are storing financial figures in a system - and when the numbers start going over 1,000,000 the number start getting rounded to the nearest 100. The full operator is:

|l10n(number)

How can I change the operator so that it just displays the exact number without any rounding, preferably with 2 decimal places?

Many thanks, Steve.

http://www.oneworldmarket.co.uk

Felipe Jaramillo

Wednesday 01 August 2007 10:15:03 am

Hi Steve,

We have now reproduced, investigated and solved the rounding issue. It is related to the default mysql database structure, where numbers (float) are 4 bytes and rounded after 6 figures by default.

We have successfully changed this to allow 15 figure numbers before rounding them. After doing the change in our test servers, it does not disrupt the existing data.

In my opinion, people should be warned about this inaccuracy as it affects any default installation and there is no alternative datatype for accurately storing long numbers other than TextLine.

This inaccuracy is present in the existing numbers 6 figure numbers and up as they are rounded. Eg. 1234567 is stored as 1234570.

To fix:

Increase length of FLOAT to 25 (8 bytes) in “data_float” field in table “ezcontentobject_attribute”, which will effectively make it a DOUBLE 8byte number, accurate to 15 figure numbers.

More info in:
http://dev.mysql.com/doc/refman/4.1/en/choosing-types.html
http://dev.mysql.com/doc/refman/4.1/en/storage-requirements.html
http://dev.mysql.com/doc/refman/4.1/en/numeric-types.html

Felipe Jaramillo
eZ Certified Extension Developer
http://www.aplyca.com | Bogotá, Colombia

eZ debug

Timing:	Jan 18 2025 11:44:37
Script start
Timing:	Jan 18 2025 11:44:37
Module start 'layout'
Timing:	Jan 18 2025 11:44:37
Module start 'content'
Timing:	Jan 18 2025 11:44:38
Module end 'content'
Timing:	Jan 18 2025 11:44:38
Script end

Main resources:

Total runtime	1.0626 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0063	587.9219	152.6250
Module start 'layout'	0.0063	0.0044	740.5469	39.4453
Module start 'content'	0.0107	1.0504	779.9922	488.2266
Module end 'content'	1.0611	0.0014	1,268.2188	8.1563
Script end	1.0625		1,276.3750

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.3123	16	0.0002
Check MTime	0.0014	0.1329	16	0.0001
Mysql Total
Database connection	0.0007	0.0622	1	0.0007
Mysqli_queries	1.0192	95.9167	54	0.0189
Looping result	0.0005	0.0497	52	0.0000
Template Total	1.0286	96.8	2	0.5143
Template load	0.0021	0.1962	2	0.0010
Template processing	1.0265	96.6024	2	0.5132
Template load and register function	0.0002	0.0163	1	0.0002
states
state_id_array	0.0009	0.0823	1	0.0009
state_identifier_array	0.0013	0.1186	2	0.0006
Override
Cache load	0.0017	0.1572	22	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0588	2	0.0003
Fetch class attribute name	0.0010	0.0929	2	0.0005
XML
Image XML parsing	0.0002	0.0234	2	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0006	2	0.0000
General
dbfile	0.0007	0.0683	10	0.0001
String conversion	0.0000	0.0008	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 8 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs