John,
I'm not sure what you mean. What do 64-bit SQLite integers do for me?
Oracle 8 uses the BCD, and I'm trying to temporarily match that.
I'm not looking for sufficient precision, I'm looking for the exact same
64 bit floating point number as from Oracle.
Liam
On Wed, Mar 26, 2008 at 9:25 PM
Ken,
Thanks for your detailed response. I thought of your remedies, but I
perhaps didn't explain myself well enough.
The Oracle we are using is Oracle 8, yes, ancient I know, but a fact
of life. It has no binary_double type; that was introduced for Oracle
10 evidently. Second, I know there is
We actually added this type of capability to Sqlite (actually fixed
point display format numbers), but it may be unnecessary in your case.
Instead of representing integers as BCD how about using the 64 bit
Sqlite integers? You may have sufficient precision. The COBOL-style
COMP3 integers are
Liam,
I know a great deal about oracle internals, Oracle stores "numbers" as you
indicate in a bcd format. But It can be up to 22 bytes long. But usage in
oracle proc/proc++/sql/plsql is really dependent upon your native conversion to
host datatype.
The number storage formats betweend Sqlite a
I am porting a numerical application from Oracle to SQLite. For the
most part, I have been successful, but there are slight disagreements
in the floating point number results. I have traced this back and
found a problem. According to
http://articles.techrepublic.com.com/5100-22_11-5224536.html,
5 matches
Mail list logo
