X-FeedAbuse: http://nntpfeed.proxad.net/ feeded by 88.191.28.29 Path: text.usenetserver.com!out01b.usenetserver.com!news.usenetserver.com!in02.usenetserver.com!news.usenetserver.com!postnews.google.com!news4.google.com!feeder1-2.proxad.net!212.27.60.67.MISMATCH!proxad.net!nntpfeed.proxad.net!news.netfinity.fr!aioe.org!not-for-mail From: Jeff Kish Newsgroups: comp.databases.oracle.misc Subject: Re: float storage Date: Thu, 07 Jun 2007 15:38:20 -0400 Organization: Aioe.org NNTP Server Lines: 29 Message-ID: References: <1181231802.220477.29140@k79g2000hse.googlegroups.com> NNTP-Posting-Host: VCA6O7C9cL8ryzdvx6XtdA.user.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Newsreader: Forte Agent 3.3/32.846 Xref: usenetserver.com comp.databases.oracle.misc:248155 X-Received-Date: Thu, 07 Jun 2007 15:37:55 EDT (text.usenetserver.com) On Thu, 07 Jun 2007 08:56:42 -0700, Wazusa Blong wrote: >On Jun 7, 10:05 am, Jeff Kish wrote: >> >NUMBER() can be declared with or without a scale, as illustrated. The >column being 'moved' from NUMBER to FLOAT requires that the precision >be reduced to allow for additional scale; that the existing data may >meet the maximum precision declared for the current definition is why >you can't simply perform an ALTER TABLE to enact this change on a >populated column. > >The documentation explains this. > > >David Fitzjarrell thanks. yeah I was confused because the docs (oracle 9i sql reference) state: "Specify a floating-point number using the following form: NUMBER The absence of precision and scale designators specifies the maximum range and precision for an Oracle number." I appreciate the clarification. I just don't know what the max size or precision we'll need is going to be, so I wanted to get a pretty large capacity for both. Jeff Kish