Re: [SQL] oracle to postgres migration question
* Bruce Momjian ([email protected]) 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. ehh, but we provide formatting functions and you can change the output format in psql to something more useful if you want (and there's always COPY too). tbh, I'm alot happier w/ psql than SQL*Plus in that regard. People who are trying to parse psql's output directly should realize they probably are going about it the wrong way. :) Stephen signature.asc Description: Digital signature
Re: [SQL] oracle to postgres migration question
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 -- Sent via pgsql-sql mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql
Re: [SQL] oracle to postgres migration question
[email protected] (Stephen Frost) writes: > People who are trying to parse psql's output directly should realize > they probably are going about it the wrong way. :) There's a set of people I need to tell that to... -- select 'cbbrowne' || '@' || 'cbbrowne.com'; http://cbbrowne.com/info/internet.html "MS apparently now has a team dedicated to tracking problems with Linux and publicizing them. I guess eventually they'll figure out this back fires... ;)" -- William Burrow -- Sent via pgsql-sql mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql
Re: [SQL] oracle to postgres migration question
On Wed, Jun 16, 2010 at 1:42 PM, Chris Browne wrote: > [email protected] (Stephen Frost) writes: >> People who are trying to parse psql's output directly should realize >> they probably are going about it the wrong way. :) > > There's a set of people I need to tell that to... If you're at least making the output something like tab, space, pipe delimited you can parse it. On systems with only bash to play with, I've done that before because it and psql were the only tools I had to work with. I wouldn't try to write some masterpiece artwork of code around psql output, but for some short scripts it's usable, and way easier than dealing with Oracle. -- Sent via pgsql-sql mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql
