From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas Lockhart) |
Cc: | zakkr(at)zf(dot)jcu(dot)cz, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Re: TO_CHAR() |
Date: | 1999-10-01 16:00:09 |
Message-ID: | m11X56P-0003kLC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > discussion join you (Thomas) and me only, but others probably needn't
> > TO_CHAR, TO_NUMBER, TO_DATE) ..?
>
> People have requested to_char(), or at least inquired about it, though
> of course there are always ways to work around not having it. After
> all, it *is* non-standard ;) But we already have some Oracle
> compatibility functions, and a few more won't hurt.
>
> There are two possibilities:
>
> 1) we incorporate it into the main tree
> 2) we distribute it as a contrib package
If incorporating into main tree, don't forget that TO_CHAR()
must also be capable to handle NUMERIC/DECIMAL/INTEGER with a
rich set of fomatting styles. Actually I'm in doubt if you
both are a little too much focusing on DATE/TIME.
This means that there could be different input arguments
(type and number!) to TO_CHAR().
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Roberto Cornacchia | 1999-10-01 16:11:51 | attribute distinct values estimate |
Previous Message | Bruce Momjian | 1999-10-01 15:45:40 | Re: [HACKERS] are subtransactions not nestable? |