From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: "oracle to postgresql" conversion |
Date: | 2007-03-09 21:25:55 |
Message-ID: | 45F1D0E3.6090209@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/09/07 14:53, Chris Fischer wrote:
> All of Oracle's (non-float) number types are variable size
> numbers with an ordinal and a mantissa. This makes Oracle number
> very efficient for smaller values as compared to fixed size
> integers, but less efficient with larger values. NUMBER has a
> maximum precision of 38 digits with a scale of -84 to +127.
> NUMBER consumes between 1 and 22 bytes on disk. It is typical to
> specify a NUMBER with (p, s). In the absence of definition,
> precision of 38 and scale indeterminate will be assumed.
>
> The exception to this are IEEE floating point number types which
> are a fixed size regardless of value.
>
> Summary: Oracle has no fixed length equivlents to tinyint,
> smallint, int or bigint from other databases and can either store
> these values more or less efficiently than those databases with
> fixed length integer types.
Wow!!!! Didn't believe you (Oracle couldn't be *that* lame, could
it?), so I Googled.
According to Table 12-1 of this web page, Oracle will silently
truncate your numbers. There are no scalar data types!!!!
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96524/c13datyp.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFF8dDjS9HxQb37XmcRArCMAKDAFuUM2V804Zjdurr6eemqPyHHOwCg1oGk
8RxOTImJVBUqdBhHK6tezkA=
=ibbT
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | ksherlock@gmail.com | 2007-03-09 21:27:51 | Re: Trigger for Audit Table |
Previous Message | Chris Fischer | 2007-03-09 20:53:40 | Re: "oracle to postgresql" conversion |