MIME-Version: 1.0
References: 
 <CAFSMqn-2nkUsB=d1FGc2ZOh_hBsqVLuLaZrR5pnBNZ8-wzpNfg@mail.gmail.com>
In-Reply-To: 
 <CAFSMqn-2nkUsB=d1FGc2ZOh_hBsqVLuLaZrR5pnBNZ8-wzpNfg@mail.gmail.com>
From: Dave Page <dpage@pgadmin.org>
Date: Fri, 24 May 2019 09:34:48 +0100
Message-ID: 
 <CA+OCxozn3uCLqhsNOD2pzeObGRUims7LnTYU45c60kjOBc_GLA@mail.gmail.com>
Subject: Re: GSoC Project Timeline and Proposal
To: Yosry Muhammad <yosrym93@gmail.com>
Cc: pgadmin-hackers <pgadmin-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000f78a2a05899e1244"
Precedence: bulk

--000000000000f78a2a05899e1244
Content-Type: text/plain; charset="UTF-8"

Hi

On Fri, May 24, 2019 at 7:40 AM Yosry Muhammad <yosrym93@gmail.com> 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

--000000000000f78a2a05899e1244
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi</div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Fri, May 24, 2019 at 7:40 AM Yosry Muhammad &lt;=
<a href=3D"mailto:yosrym93@gmail.com">yosrym93@gmail.com</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><d=
iv>Dear all,</div><div><br></div><div>The official coding phase for GSoC st=
arts 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.</div><div><br></d=
iv><div>Anyway, I would like to use this time to evaluate my timeline and p=
lan and make any necessary corrections, create milestones, etc.</div><div><=
br></div><div>I would really appreciate it if you all took the time (especi=
ally my mentor, Mr. Page) to go through my project proposal and timeline an=
d give me your suggestions and feedback.</div></div></blockquote><div><br><=
/div><div>I think the timeline looks fine. As they say though, no battle pl=
ans survive first contact with the enemy. The same often applies with softw=
are engineering; expect the unexpected, and expect to change plans and adap=
t.</div><div><br></div><div>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 e=
asier, to have that in the server for possible reuse, and because you&#39;l=
l have direct access to psycopg2 and the database connections there.</div><=
div>=C2=A0</div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature">Dav=
e Page<br>Blog: <a href=3D"http://pgsnake.blogspot.com" target=3D"_blank">h=
ttp://pgsnake.blogspot.com</a><br>Twitter: @pgsnake<br><br>EnterpriseDB UK:=
 <a href=3D"http://www.enterprisedb.com" target=3D"_blank">http://www.enter=
prisedb.com</a><br>The Enterprise PostgreSQL Company<br></div></div>

--000000000000f78a2a05899e1244--