Thanks Zoran,
Will fix this before pushing.
Waiting also for comments and/or ack from Neelakanta.
/AndersBj
-Original Message-
From: Zoran Milinkovic
Sent: den 8 april 2014 16:56
To: Anders Björnerstedt; reddy.neelaka...@oracle.com
Cc: opensaf-devel@lists.sourceforge.net
Subject:
Hi Zoran,
Reviewed and tested the patch.
Ack.
The published patch, work fine when dumping for float and double is for
xml format.
where as either in PBE or in dumpcase the precision is not yet followed
(probably a new ticket may be created for fixing at later stage)
/Neel.
On Tuesday 25
Hi Neelakanta,
Can you be more specific where the precision is not followed ?
There is no need for another ticket. We can fix it in this ticket.
Best regards,
Zoran
-Original Message-
From: Neelakanta Reddy [mailto:reddy.neelaka...@oracle.com]
Sent: den 9 april 2014 12:46
To: Zoran
Hi zoran,
when we dump to a db eg:
immdump -p /tmp/dump.db
and try to open the db, you still see the precession is not
followed(same with PBE).
#sqlite3 /tmp/dump.db .dump /tmp/dump.sql
Eg:
# immlist testClass=1
Name Type Value(s)
Hi Neelakanta,
It seems that sqlite has a problem in keeping floating point precision using
sqlite3_column_text. It could be a bug in sqlite.
Unfortunately, we use sqlite3_column_text() for all data types, including float
and double.
I'll write a new ticket for fixing immload to use a correct
