Hi,
To implement my local calendar, I tried adding a new type (pdate) to pgsql
as an extension. At first I used a struct of size 6, and I returned a
pointer to it in pdate_in with no problem. Now I changed the type to int32,
returning PG_RETURN_INT32. I removed all palloc calls. but the server
Mohsen Alimomeni m.alimom...@gmail.com writes:
Hi,
To implement my local calendar, I tried adding a new type (pdate) to pgsql
as an extension. At first I used a struct of size 6, and I returned a
pointer to it in pdate_in with no problem. Now I changed the type to int32,
returning
Hi everyone,
I want to try to add a multi calendar system for pgsql. I want to know if it
will be accepted as a patch to pgsql?
More details:
Multi calendar systems are useful for several languages and countries using
different calendar: Hijri, Persian, Hebrew, etc.
For implementation I think it
Mohsen Alimomeni m.alimom...@gmail.com writes:
I want to try to add a multi calendar system for pgsql. I want to know if it
will be accepted as a patch to pgsql?
There's probably about zero chance of accepting such a thing into core,
but maybe you could do it as an add-on (pgfoundry project).
I want to try to add a multi calendar system for pgsql. I want to know if it
will be accepted as a patch to pgsql?
More details:
Multi calendar systems are useful for several languages and countries using
different calendar: Hijri, Persian, Hebrew,
etc.
For implementation I think it is
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
m.alimom...@gmail.com (Mohsen Alimomeni) writes:
I want to try to add a multi calendar system for pgsql. I want to
know if it will be accepted as a patch to pgsql?
I would expect there to be nearly zero chance of such, at least in the
form of a change to how dates are stored.
As long as there
