From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | ben hockey <neonstalwart(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Mike Fowler <mike(at)mlfowler(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: ecmascript 5 DATESTYLE |
Date: | 2011-12-06 22:24:50 |
Message-ID: | CAFj8pRCEVRNFRZpCjA++YT-tBX5Zg0DZi+KT=c325075J7aRPA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello
2011/12/6 ben hockey <neonstalwart(at)gmail(dot)com>:
> i may have spoken a little too soon about the format being right... i just
> took a look at the postgres source code and it would need one more change to
> completely meet my needs. EncodeDateTime should put a 'Z' for UTC timezone
> rather than '+0'. with this being the case, do you think there would need
> to be an ECMA datestyle or would XSD be compatible with this change?
>
probably we can't to change a XSD format - but new format, that is
exactly ECMA should not be problem.
> i haven't touched any c code in quite a while but the changes look simple
> enough that i could work towards an ECMA patch if that's the best way to go
> about this.
you can become a postgreql's hacker :) - anybody starts on simple jobs
PostgreSQL hacking is good lecture
Pavel
>
> thanks,
>
> ben...
From | Date | Subject | |
---|---|---|---|
Next Message | Marti Raudsepp | 2011-12-06 22:29:22 | Re: [PATCH] Caching for stable expressions with constant arguments v3 |
Previous Message | ben hockey | 2011-12-06 22:15:16 | Re: ecmascript 5 DATESTYLE |