public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dave Page <[email protected]>
To: Yosry Muhammad <[email protected]>
Cc: pgadmin-hackers <[email protected]>
Subject: Re: GSoC Project Timeline and Proposal
Date: Fri, 24 May 2019 09:34:48 +0100
Message-ID: <CA+OCxozn3uCLqhsNOD2pzeObGRUims7LnTYU45c60kjOBc_GLA@mail.gmail.com> (raw)
In-Reply-To: <CAFSMqn-2nkUsB=d1FGc2ZOh_hBsqVLuLaZrR5pnBNZ8-wzpNfg@mail.gmail.com>
References: <CAFSMqn-2nkUsB=d1FGc2ZOh_hBsqVLuLaZrR5pnBNZ8-wzpNfg@mail.gmail.com>
Hi
On Fri, May 24, 2019 at 7:40 AM Yosry Muhammad <[email protected]> wrote:
> Dear all,
>
> The official coding phase for GSoC starts by May 27th. As I have stated in
> my previous email, I will not be able to start working until the 2nd of
> June, however, I will compensate for the lost time by working extra during
> the first week or two.
>
> Anyway, I would like to use this time to evaluate my timeline and plan and
> make any necessary corrections, create milestones, etc.
>
> I would really appreciate it if you all took the time (especially my
> mentor, Mr. Page) to go through my project proposal and timeline and give
> me your suggestions and feedback.
>
I think the timeline looks fine. As they say though, no battle plans
survive first contact with the enemy. The same often applies with software
engineering; expect the unexpected, and expect to change plans and adapt.
One thought that did cross my mind; I wonder if the detection of the query
result type (e.g updateable vs. non-updateable) should be handled in a
backend function? It might be useful, and perhaps easier, to have that in
the server for possible reuse, and because you'll have direct access to
psycopg2 and the database connections there.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: GSoC Project Timeline and Proposal
In-Reply-To: <CA+OCxozn3uCLqhsNOD2pzeObGRUims7LnTYU45c60kjOBc_GLA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox