Re: CVS commit: pkgsrc/databases/py-postgresql

[Leonardo Taccari <leot%NetBSD.org@localhost>]

Hello David,

David Maxwell writes:
> [...]
> Log Message:
> Update to PyGreSQL version 5.1  (commit on behalf of darcy@)
> [...]

Thanks for updating it!

When updating packages please always add a changelog if possible in the
commit message.

>From <http://pygresql.org/contents/changelog.html>:

Version 5.1 (2019-05-17)
------------------------
 * Changes to the classic PyGreSQL module (pg):
    o Support for prepared statements (following a suggestion and first
      implementation by Justin Pryzby on the mailing list).
    o DB wrapper objects based on existing connections can now be closed
      and reopened properly (but the underlying connection will not be
      affected).
    o The query object can now be used as an iterator similar to
      query.getresult() and will then yield the rows as tuples. Thanks to
      Justin Pryzby for the proposal and most of the implementation.
    o Deprecated query.ntuples() in the classic API, since len(query) can
      now be used and returns the same number.
    o The i-th row of the result can now be accessed as query[i].
    o New method query.scalarresult() that gets only the first field of
      each row as a list of scalar values.
    o New methods query.one(), query.onenamed(), query.onedict() and
      query.onescalar() that fetch only one row from the result or None
      if there are no more rows, similar to the cursor.fetchone() method
      in DB-API 2.
    o New methods query.single(), query.singlenamed(), query.singledict()
      and query.singlescalar() that fetch only one row from the result,
      and raise an error if the result does not have exactly one row.
    o New methods query.dictiter(), query.namediter() and
      query.scalariter() returning the same values as query.dictresult(),
      query.namedresult() and query.salarresult(), but as iterables
      instead of lists. This avoids creating a Python list of all results
      and can be slightly more efficient.
    o Removed pg.get/set_namedresult. You can configure the named tuples
      factory with the pg.set_row_factory_size() function and change the
      implementation with pg.set_query_helpers(), but this is not
      recommended and this function is not part of the official API.
    o Added new connection attributes socket, backend_pid, ssl_in_use and
      ssl_attributes (the latter need PostgreSQL >= 9.5 on the client).

 * Changes to the DB-API 2 module (pgdb):
    o Connections now have an autocommit attribute which is set to False
      by default but can be set to True to switch to autocommit mode
      where no transactions are started and calling commit() is not
      required. Note that this is not part of the DB-API 2 standard.

Vesion 5.0.7 (2019-05-17)
-------------------------
 * This version officially supports the new PostgreSQL 11.
 * Fixed a bug in parsing array subscript ranges (reported by Justin Pryzby).
 * Fixed an issue when deleting a DB wrapper object with the underlying
   connection already closed (bug report by Jacob Champion).


Thank you!