On Sat, Aug 04, 2012 at 12:11:56PM -0400, Tom Lane wrote:
More generally, nobody is maintaining ecpg's copy of the datetime code,
and that's been true for a very long time. I'm not personally
Well, maintaining as in fixing bugs I do as I find time. Maintaining as in
keeping in sync with the
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Saturday, August 04, 2012 1:48 AM
Amit Kapila amit.kap...@huawei.com writes:
select (interval '56:48' minute to second);
result$B!'(B00:56:48
select (interval '-56:48' minute to second);
result$B!'(B-56:48:00
select (interval '+56:48'
Amit Kapila amit.kap...@huawei.com writes:
Yes, this is right that tmask need not be changed, also one more thing I
have noticed that
in file Interval.c also there is a function DecodeInterval() which is
currently little different
from DecodeInterval() in datetime.c for DTK_TZ case.
For
Amit Kapila amit.kap...@huawei.com writes:
select (interval '56:48' minute to second);
result$B!'(B00:56:48
select (interval '-56:48' minute to second);
result$B!'(B-56:48:00
select (interval '+56:48' minute to second);
result$B!'(B56:48:00
I have checked the code and found that
select (interval '56:48' minute to second);
result：00:56:48
select (interval '-56:48' minute to second);
result：-56:48:00
select (interval '+56:48' minute to second);
result：56:48:00
When user uses ‘+’ or ‘-‘ symbol, then minute to second range is getting
ignored.
I have checked the code
