Newt-db

Latest version: v0.9.0

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

Scan your dependencies

Page 1 of 3

0.9.1

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

- Nothing changed yet.

0.9.0

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

- Added an experimental feature to update auxiliary tables to support
indexing data that comes from multiple newt records. (More on this
later if initial experiment confirm the usefulness of this
feature.)

0.8.0

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

- Changed the way records are written to the ``newt`` table:

- Records are written in object id order.

- Updated are applied using "upserts" so that records don't
disappear during the update process, which previously caused
breakage when PostgreSQL operations during update (triggers or
indexes) examined multiple records.

- Postgres 9.5 or later is now required.

0.7.0

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

- Fixed: newt.db.search.query_data didn't accept an ordinary ZODB connection.

- The methods in newt.db.search that accept a connection now
accept a database object (in addition to a Newt or ZODB connection).

0.6.0

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

- Add a -x/--transform option to the updater to specify a
data-transformation function.

0.5.3

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

- Fixed: Newt DB couldn't be added to an existing RelStorage database.

- Removed the updater ``--redo`` option. It was implemented incorrectly.
Implementing it correctly will be necessary at some point, but for
now, we'll punt.

- Added a new ``--compute-missing`` option to compute missing Newt
records after updating an application from plain RelStorage. (This
is similar to the removed ``--redo`` but simpler and narrower in
scope.)

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.