Re: [OT] Lack of IEEE values in Oracle

Obviously my next comments relate more to application requirements than the raw input - but even if I had a facility for storing the incoming data in its incoming form (which you do in Oracle with the RAW type), I would probably look at splitting the stream into three tables -

    Values within the specified range
    Special values known to be messages
    Values deemed to be garbage

But I can appreciate why you think it is vital to store numbers as IEEE format.

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Host to The Co-Operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

Author of:
Practical Oracle 8i: Building Efficient Databases

Screen saver or Life saver: http://www.ud.com
Use spare CPU to assist in cancer research.

Murray Peterson wrote in message ...


>What we retrieve from the database  must be guaranteed to be identical to

>what came in from the field -- even a single bit error can't be tolerated.

>If at any time the device sends a value (no matter how erroneous or

>unexpected), the database *must* be able to store that value, even if it is

>unexpected from the original design.  In other words, I may never expect

>the values 1.0e-100 and 1.0e+1000, but if they show up, then I must store

>them for later retrieval -- an error message is not an accepatble option.