Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Long Integers and Oracle Numbers

Re: Long Integers and Oracle Numbers

From: Mike Burden <michael.burden_at_capgemini.co.uk>
Date: Fri, 19 Mar 1999 17:06:22 +0000
Message-ID: <36F2840D.E044ECB3@capgemini.co.uk>


It's not quite as bad as it sounds. All numeric fields are variable length (including integer) so if you store 0 to 255 you will only use 3 bytes max. Use vszie function confirm. Still two more than you wish.

darren_reynolds1118_at_my-dejanews.com wrote:

> I'm used to working with systems where you worry about the speed of
> execution. If you have a field you know will only ever hold values 0-255, you
> call it a Byte. 0-~2bn is a Long Integer.
>
> So along came Oracle 8, and I had to design a data model. All the
> documentation says that for any integer, you should use Number(38). According
> to the same documentation, this is allows for the storage of up to 38 digits,
> with decimal point anywhere. Now, I know that this will probably work, but it
> doesn't sound like a terribly optimal way of going about storing a 32-bit
> Long Integer.
>
> Does anyone know anything about how Oracle handles Number fields internally?
> Is there anything to be gained by using, say Number(10) over Number(38), and
> ignoring the documentation?
>
> Thanks in advance!
>
> Darren Reynolds,
> Halifax plc, England
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Received on Fri Mar 19 1999 - 11:06:22 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US