Gocept-testdb

Latest version: v1.3

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

Scan your dependencies

Page 3 of 3

1.0b1

------------------

- Changed the protocol for using test databases: separated instantiating a
Database instance from creating the database on the server. Creating
Database instances is cheap now so they can be interacted with and passed
around, deferring the expensive database creation on the server to the
moment db.create() is called explicitly. This is also more symmetric with
respect to db.drop().

- Added functionality for dropping all databases matching the testdb naming
scheme which may have been left on the server by earlier test runs.
Optionally also drops the template db.

- Added option to specify the name of the database for MySQL and PostgreSQL.

- Added an option to specify a template database for PostgreSQL. If it does
not exist, it is created from the specified schema. It is also possible to
force the creation of the template even if it exists (dropping the current
template database). Whenever the schema has changed since the template db
was last created, the template db is updated automatically.

0.4

----------------

- Added option to specify the encoding for the PostgreSQL database.

- Updated PostgreSQL protocol from ``postgres:`` to ``postgresql:`` as the
former one is deprecated in SQLAlchemy 0.6, thus requiring atleast version
0.5.6 of SQLAlchemy.

- Added documentation how to develop this package further.

- Added doumentation about usage of `Database prefix`.

0.3

----------------

- PostgreSQL: Don't call createdb/dropdb with ``--quite`` but only psql.

0.2

----------------

- implemented authentication with password for mysql.
Passwords for postgres are still not supported, though.

0.1

----------------

- first release

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.