Re: pg_dumplo, thanks :) (fwd) - Mailing list pgsql-hackers

From Karel Zak
Subject Re: pg_dumplo, thanks :) (fwd)
Date
Msg-id Pine.LNX.3.96.1000406201231.6858A-100000@ara.zf.jcu.cz
Whole thread Raw
In response to Re: pg_dumplo, thanks :) (fwd)  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: pg_dumplo, thanks :) (fwd)  (Don Baccus <dhogaza@pacifier.com>)
List pgsql-hackers
On Thu, 6 Apr 2000, Bruce Momjian wrote:

> > Since you've conveniently made a post that reached my mailbox right after
> > a query from someone working on our toolkit port from Oracle to PG, did you 
> > know that in Oracle to_char formatting chars don't have to be upper case?
> > 
> > In other words something like "to_char(sysdate, 'yyyy-mm-dd')" formats
> > sysdate rather than ignore the formatting characters.  Turns out the
> > toolkit we're porting from Oracle almost always uses upper case, but
> > not always and one of our gang just ran into this earlier this morning
> > while porting over one of the toolkit module...
> 
> Doesn't the upper/lower affect how the result displays.  I think that is
> a cool effect.
Thanks Don. I tomorrow check it and comperate it with Oracle and if is here
a problem I fix it. In stable 7.0 it will right. 
PG's to_char() is based on upper case. Hmm, but it is not easy, it must be 
case sensitive for some format-pictures (like to_char(now(), 'Day') and for 
to_char(now(), 'yyyy') is upper/lower without effect. I fix it and add this
feature to internal to_char's parser. 

                        Karel





pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_dumplo, thanks :) (fwd)
Next
From: Don Baccus
Date:
Subject: Re: pg_dumplo, thanks :) (fwd)