From: | Sam Mason <sam(at)samason(dot)me(dot)uk> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Multi calendar system for pgsql |
Date: | 2009-02-18 17:46:11 |
Message-ID: | 20090218174611.GR32672@frubble.xen.chris-lamb.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 18, 2009 at 07:50:31PM +0330, Mohsen Alimomeni wrote:
> Multi calendar systems are useful for several languages and countries using
> different calendar: Hijri, Persian, Hebrew, etc.
When would the differences between these calenders actually show
up? I can only think of it affecting input/output routines and the
date_part,date_trunc,to_date and to_char routines. But am I missing
something?
If that's all, then how about just treating the current PG
date types as Julian days (as far as I know, that's how it's
treated internally anyway) and providing a multi-calender set of
date_part,date_trunc,to_date and to_char routines. I.e. leave out the
input/output routines.
Doing this would be much easier, but less fun, than creating whole new
types and having to modify the parser as well to recognize the new
syntax.
--
Sam http://samason.me.uk/
From | Date | Subject | |
---|---|---|---|
Next Message | ohp | 2009-02-18 17:55:53 | pg_restore new option -m |
Previous Message | Joshua D. Drake | 2009-02-18 17:33:38 | Re: The science of optimization in practical terms? |