From: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Vik Fearing <vik(dot)fearing(at)enterprisedb(dot)com> |
Subject: | Calendar support in localization |
Date: | 2021-03-15 14:47:49 |
Message-ID: | CALAY4q99QdH7bw-Rtr6L1Bk0eu_7zo-m9bH5Y08mRLWSpYNFTA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all,
My country(Ethiopia) is one of the nations that uses different kind of
calendar than what PostgreSQL have so we are deprived from the benefit of
data datatype. We just uses String to store date that limits our
application quality greatly. The lag became even worst once application and
system time support is available and it seems to me it is not fair to
suggest to add other date data type kind and implementation for just
different calendar that even not minor user group. Having calendar support
to localization will be very very very very exciting feature for none
Gregorian calendar user group and make so loved. As far as i can see the
difficult thing is understanding different calendar. I can prepare a patch
for Ethiopian calendar once we have consensus.
I cc Thomas Munro and Vik because they have interest on this area
Please don't suggests to fork from PostgreSQL just for this feature
regards
Surafel
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Dilger | 2021-03-15 15:11:29 | Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index. |
Previous Message | vignesh C | 2021-03-15 14:35:40 | Re: locking [user] catalog tables vs 2pc vs logical rep |