Pugsql

Latest version: v0.2.4

Safety actively analyzes 622360 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 4

0.2.4

* Transactions are now automatically committed when leaving a transaction context when using nested transactions, thanks to [Oleksandr Fedorov](https://github.com/o-fedorov/).
* Improved feedback when mistakenly passing positional arguments to statements that don't support it.
* Dropped support for Python 3.5 and 3.6.
* Added test coverage for some postgres-specific tests.
* Migrated test suite from TravisCI to GitHub Actions.
* Fixed broken test suite on Python 3.10

0.2.3

* Fixes Python 3.5 tests which were broken in 0.2.2. Began release testing with 3.8.

0.2.2

* Support for nested transactions [40](https://github.com/mcfunley/pugsql/issues/40) thanks to [Hosein Yeganloo](https://github.com/Yeganloo).
* Modules expose the [SQLAlchemy engine](https://docs.sqlalchemy.org/en/13/core/connections.html#sqlalchemy.engine.Engine) they are using ([5](https://github.com/mcfunley/pugsql/issues/5)).

0.2.1

* Added support for adding queries from another path to a module (see [29](https://github.com/mcfunley/pugsql/issues/29)).

0.2.0

* Dropped automatic caching of modules. See [19](https://github.com/mcfunley/pugsql/issues/19) for discussion.

0.1.19

* An `encoding` parameter for interpreting sql files can be passed when creating a pugsql module, thanks to [newturok](https://github.com/newturok).
* Better exception feedback when calling statements incorrectly with positional arguments.
* Added some development setup notes to the README.

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.