Pugsql

Latest version: v0.3.1

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

Scan your dependencies

Page 3 of 4

0.1.14

* `IN` clauses also accept `set` parameters (in addition to `tuple` and `list`).

0.1.13

* `IN` clauses now work. Passing a tuple or a list as the value of a named parameter will automatically treat the parameter as an expanding (i.e. `(?, ?, ?, ?)`, etc) bind parameter.

0.1.12

* Added support for passing `multiparams` through to SQLAlchemy's `execute` method, which among other things makes multi-row inserts work ([9](https://github.com/mcfunley/pugsql/issues/9)).
* Parsed statements use very slightly less memory.

0.1.11

* Added the `:scalar` return type, which returns the first value in the first row.
* The `:insert` return type defaults to `:scalar` behavior when a DBAPI does not support `lastrowid` ([7](https://github.com/mcfunley/pugsql/issues/7)).

0.1.10

* Fixed [11](https://github.com/mcfunley/pugsql/issues/11), exception when a PugSQL module is initialized on another thread.
* Documentation fixes.

0.1.9

* Added support for `Module.transaction()`, which returns a context manager which maintains thread-local transaction scope.

Page 3 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.