| From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Hackers List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Per-database/schema settings |
| Date: | 2000-07-10 07:40:13 |
| Message-ID: | Pine.LNX.3.96.1000710093345.24431H-100000@ara.zf.jcu.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 10 Jul 2000, Karel Zak wrote:
>
> I don't know how much problematic it is, but the oracle has this feature
> (NSL_DATE_FORMAT in ALTER SESSION, etc)
Note, I see Oracle's docs, and NSL_DATE_FORMAT is probably used as
default format template for to_char/to_date, and it allowe
SELECT TO_CHAR(sysdate) FROM DUAL;
(is possible in Oracle formatting/parsing datetime without to_char(), like
postgresql timestamp_in/out?)
Hmm, PG and Oracle date/time design is probably more different. I was not
total right in the previous letter.
Karel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Przem Kowalczyk | 2000-07-10 07:51:28 | Counting affected rows |
| Previous Message | Karel Zak | 2000-07-10 07:32:37 | Re: Re: [BUGS] Unnexpected results using to_number() |