Re: GSoC Project Timeline and Proposal

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: GSoC Project Timeline and Proposal
Дата
Msg-id CA+OCxozn3uCLqhsNOD2pzeObGRUims7LnTYU45c60kjOBc_GLA@mail.gmail.com
обсуждение исходный текст
Ответ на GSoC Project Timeline and Proposal  (Yosry Muhammad <yosrym93@gmail.com>)
Список pgadmin-hackers
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

В списке pgadmin-hackers по дате отправления:

Предыдущее
От: Yosry Muhammad
Дата:
Сообщение: Re: GSoC Project Timeline and Proposal
Следующее
От: Dave Page
Дата:
Сообщение: pgAdmin 4 commit: Add a missing fix.