Re: [HACKERS] QSoC proposal: date_trunc supporting intervals

2014-03-20 Thread Claudio Freire
On Thu, Mar 20, 2014 at 5:55 PM, Alexandr wrote: >> Subtracting to get an interval, then converting that interval to seconds >> or minutes could give you a value that's wildly different from the right >> answer. > > Can you explain me when it happens ? '1 month'::interval It's different dependi

Re: [HACKERS] QSoC proposal: date_trunc supporting intervals

2014-03-20 Thread Alexandr
Subtracting to get an interval, then converting that interval to seconds or minutes could give you a value that’s wildly different from the right answer. Can you explain me when it happens ? With best wishes, Alexander S. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or

Re: [HACKERS] QSoC proposal: date_trunc supporting intervals

2014-03-20 Thread Alvaro Herrera
Alexandr escribió: > > 21.03.2014 00:33, Josh Berkus пишет: > >Comments: > >#2: I don't understand this one? > >#3 is already a patch for version 9.4, but possibly you can > >improve/expand it. > >#4 has already been the subject of a LOT of debate, I think you > >don't want to get into it. > I mea

Re: [HACKERS] QSoC proposal: date_trunc supporting intervals

2014-03-20 Thread Josh Berkus
> I meaned this one: Allow TIMESTAMP WITH TIME ZONE to store the original > timezone information, either zone name or offset from UTC > And which ideas can you advise me to add to proposal? That one has also been hotly debated. You'd probably have to do it as an extension, and that would be a fa

Re: [HACKERS] QSoC proposal: date_trunc supporting intervals

2014-03-20 Thread Alexandr
21.03.2014 00:33, Josh Berkus пишет: Comments: #2: I don't understand this one? #3 is already a patch for version 9.4, but possibly you can improve/expand it. #4 has already been the subject of a LOT of debate, I think you don't want to get into it. I meaned this one: Allow TIMESTAMP WITH TIM

Re: [HACKERS] QSoC proposal: date_trunc supporting intervals

2014-03-20 Thread Steve Atkins
On Mar 20, 2014, at 1:24 PM, Thom Brown wrote: > On 20 March 2014 20:07, Josh Berkus wrote: >> On 03/20/2014 09:56 AM, Alexandr wrote: >>> Here is the text of my proposal which I've applied to GSoC. >>> (and link >>> https://docs.google.com/document/d/1vBjQzhFT_fgoIkoEP5TVeyFA6ggsYlLq76tghGVUD6

Re: [HACKERS] QSoC proposal: date_trunc supporting intervals

2014-03-20 Thread Josh Berkus
On 03/20/2014 01:26 PM, Alexandr wrote: > > 21.03.2014 00:07, Josh Berkus пишет: >> Per my comments on the GSOC app, it looks good, but I'd like to see >> some "stretch goals" if you are able to implement the new function >> before GSOC is over. For example, one thing which has been frequently >>

Re: [HACKERS] QSoC proposal: date_trunc supporting intervals

2014-03-20 Thread Alexandr
21.03.2014 00:07, Josh Berkus пишет: Per my comments on the GSOC app, it looks good, but I'd like to see some "stretch goals" if you are able to implement the new function before GSOC is over. For example, one thing which has been frequently requested is functions to display intervals in the u

Re: [HACKERS] QSoC proposal: date_trunc supporting intervals

2014-03-20 Thread Thom Brown
On 20 March 2014 20:07, Josh Berkus wrote: > On 03/20/2014 09:56 AM, Alexandr wrote: >> Here is the text of my proposal which I've applied to GSoC. >> (and link >> https://docs.google.com/document/d/1vBjQzhFT_fgoIkoEP5TVeyFA6ggsYlLq76tghGVUD6A/edit?usp=sharing) >> >> Any suggestions and comments a

Re: [HACKERS] QSoC proposal: date_trunc supporting intervals

2014-03-20 Thread Josh Berkus
On 03/20/2014 09:56 AM, Alexandr wrote: > Here is the text of my proposal which I've applied to GSoC. > (and link > https://docs.google.com/document/d/1vBjQzhFT_fgoIkoEP5TVeyFA6ggsYlLq76tghGVUD6A/edit?usp=sharing) > > Any suggestions and comments are welcome. > Because I don't know the code of Pos

[HACKERS] QSoC proposal: date_trunc supporting intervals

2014-03-20 Thread Alexandr
Hello! Here is the text of my proposal which I've applied to GSoC. (and link https://docs.google.com/document/d/1vBjQzhFT_fgoIkoEP5TVeyFA6ggsYlLq76tghGVUD6A/edit?usp=sharing) Any suggestions and comments are welcome. Because I don't know the code of PostgreSQL well I decide not to participate i