Re: Adding an informative object to the connection

Поиск
Список
Период
Сортировка
От Murtuza Zabuawala
Тема Re: Adding an informative object to the connection
Дата
Msg-id CAKKotZQS=cB5nHpKhXEY7nK7hfKhymqrL_f26sjy80Gj0bx+TA@mail.gmail.com
обсуждение исходный текст
Ответ на Adding an informative object to the connection  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
Список psycopg
+1

--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



On Fri, Oct 12, 2018 at 10:16 PM Daniele Varrazzo <daniele.varrazzo@gmail.com> wrote:
Hi,

a few days ago we were contributed a merge request for an `.host`
attribute on the connection. But looking back at the bug
(https://github.com/psycopg/psycopg2/issues/726) I had already noticed
there are other interesting informative connection functions in the
libpq. Some of them are already exposed as methods of the connection
class (e.g. get_backend_pid(), get_transaction_status() etc), but I
can see a trickle of requests for others, so I'd rather expose
most/all of them.

Instead of bloating the connection class with more and more attributes
and methods, I'm rather adding a connection.info method to retrieve
pgconn-specific information. The work is happening in this branch:

https://github.com/psycopg/psycopg2/commits/connection-info

I would softly deprecate the currently exposed informative methods:
not sending them away in a short time but giving a preference to use
from the 'info' object what belongs to the pgconn/libpq and to leave
on the connection things regarding the Python layer, and clean up the
interfaces a little bit.

Any input is welcome. Cheers!

-- Daniele

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

Предыдущее
От: Marco De Paoli
Дата:
Сообщение: Re: Adding an informative object to the connection
Следующее
От: Daniele Varrazzo
Дата:
Сообщение: Feature branches merged to master for 2.8 release