Android Question Float type is wrong!

[LucaMs]

I read some posts on this topic.
I have always read that it is not in the internal representation.

I rather think so.

Create a SQLite table with a field of type:
test 1) Column data type = NUMERIC
test 2) Column data type = TEXT

Insert some values:

Private Query As String
Query = "INSERT INTO TB (Price) VALUES (?)"
Price = 10.1
DB.ExecNonQuery2(Query, Array As Object(Price))

You'll get:

1) NUMERIC - NOT ROUNDING
Listview data (loaded from DB): correct
DB data: WRONG

1a) NUMERIC - ROUNDING INTO THE QUERY
Listview data (loaded from DB): correct
DB data: correct

1b) NUMERIC - ROUNDING THE FLOAT VALUES SETTING THE VARIABLES
Listview data (loaded from DB): correct
DB data: WRONG

-------------------------------------------------------------------

2) TEXT - NOT ROUNDING
Listview data (loaded from DB): WRONG
DB data: WRONG

 

[Erel]

But how many know that the value returned by Log is different from what a Java user would get for the same number? Who is right in this case? Does the conversion to double made by B4A brings something useful?

I think that it doesn't really matter. Developers should 1. remember that a binary floating point cannot accurately represent decimal values.
2. use NumberFormat if they want to convert a number to a string.

 

[LucaMs]

I had to assume the use of -1 for the MinimumIntegers.
I think it should be in the example ("Intellisense")

 

[Erel]

What is the difference between 0 and -1 in this case?

 

[LucaMs]

What is the difference between 0 and -1 in this case?

zero?

I would think that the function would return zero integers using 0, then only the decimal part.

In fact, I did not think to use 0 but -1 (or Null).

0 is not even in the "Intellisense"

 

[Erel]

The MinimumIntegers parameter specifies the minimum number of integers. If you don't want to add any padding zeroes then you should set the minimum number of integers to 0.

It is 0 in the first example: http://www.b4x.com/android/forum/pages/results/?query=numberformat&page=1&prefix=0

 

[LucaMs]

I think, rightly , that it should be specified here:

and I also think that 0 is misleading.