Message-ID: <4C18BA8A.1050307@ttitech.net>
Date: Wed, 16 Jun 2010 07:50:34 -0400
From: Joshua Gooding <JGooding@ttitech.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
	rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
Subject: Re: oracle to postgres migration question
References: <201006152245.o5FMj4t10356@momjian.us>
 <4C185AD3.8050701@bankir.ru>
In-Reply-To: <4C185AD3.8050701@bankir.ru>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 6/16/2010 1:02 AM, silly sad wrote:
> On 06/16/10 02:45, Bruce Momjian wrote:
>> Scott Marlowe wrote:
>>> Note that psql automagically right justifies numerics and dynamically
>>> sizes all columns so you don't have to do as much of this stuff.
>>> Oracle always made me feel like I was operating the machine behind the
>>> curtain in the Wizard of Oz, lots of handles and switches and knobs I
>>> had to mess with to get useful output.
>>
>> Yeah, I have heard that description many times in other forms.
>
> count me in :-)
>
> i even suspect this exactly is a Secret of the oracle Power.
> "higher performance through lower level of control"
>
>
sorry for the delay guys, and thank you for all the replies.

The problem I was having, is the data in field 'track_start' was a 
number type in oracle.  I switched it out to a real in postgres, however 
when I displayed the column (via psql) it was printing out for example 
(1.23546e12).  I know you could format the output via Sql Plus but I was 
not sure what (if anything) you could do in postgres for that.  That 
being said, I then re-modified the field type and it displays properly.  
I went from a real to a integer type and it seemed to clear up every 
issue I was having (both displaying and programatically)

-- 
Joshua Gooding
Software Engineer
TTi Technologies Wheeling, WV 26003

w: 304-233-5680 x 308
c: 304-794-8341