| From: | hitesh ramani <hiteshramani(at)hotmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GSoC 2015: Introduction and Doubt regarding a Project. |
| Date: | 2015-03-17 20:28:49 |
| Message-ID: | BAY176-W42E83CF8B1C32FBE5E6FD0DC030@phx.gbl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Peter,
> > 1. As I did some research on this project, I found *date_trunc()
> > supporting intervals *was suggested last year but not selected as a
> > GSoC project. Is it being floated this year too(as mentioned on the GSoC
> > 2015 wiki page of Postgres)? If yes, what are the exact expected outputs?
>
> It seems to me that that would be too small for a GSoC project.
I agree, but I saw the project mentioned on the GSoC wiki page of Postgres, and that's why I was curious to know the expected outputs, because if it was considered to be floated as a GSoC project, there must be something more than just what the title depicts.
--Hitesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-03-17 21:28:30 | Re: Rethinking the parameter access hooks for plpgsql's benefit |
| Previous Message | Peter Eisentraut | 2015-03-17 20:23:32 | Re: GSoC 2015: Introduction and Doubt regarding a Project. |