cone.zodb 1.1.0
ZODB integration for cone.app
License: Simplified BSD
Requires Python: >=3.10
Keywords: cone, node, pyramid, web

cone.zodb
=========

.. image:: https://img.shields.io/pypi/v/cone.zodb.svg
    :target: https://pypi.python.org/pypi/cone.zodb
    :alt: Latest PyPI version

.. image:: https://img.shields.io/pypi/dm/cone.zodb.svg
    :target: https://pypi.python.org/pypi/cone.zodb
    :alt: Number of PyPI downloads

.. image:: https://github.com/conestack/cone.zodb/actions/workflows/test.yaml/badge.svg
    :target: https://github.com/conestack/cone.zodb/actions/workflows/test.yaml
    :alt: Test cone.zodb

This package provides ZODB integration in ``cone.app`` and basic
application nodes for publishing ZODB models.


Changes
=======

1.1.0 (2026-02-03)
------------------

- Refactor package layout to use ``pyproject.toml`` and implicit namespace packages.
  [rnix]

- Setup Makefile.
  [lenadax]

- Run tests with pytest.
  [lenadax]


1.0 (2025-10-25)
----------------

- Pin upper versions of dependencies.
  [rnix]

- Setup Makefile.
  [lenadax]

- Run tests with pytest.
  [lenadax]


1.0a3 (2022-10-06)
------------------

- Replace deprecated use of ``IStorage`` by ``IMappingStorage``.
  [rnix]

- Replace deprecated use of ``Storage`` by ``MappingStorage``.
  [rnix]

- Replace deprecated use of ``Nodify`` by ``MappingNode``.
  [rnix]

- Replace deprecated use of ``NodeChildValidate`` by ``MappingConstraints``.
  [rnix]


1.0a2 (2021-10-21)
------------------

- Implement ``node.iterfaces.IOrder`` on ``ZODBEntry``.
  [rnix]


1.0a1 (2020-07-09)
------------------

- Fix case where ``_v_parent`` is not set if ``ZODBEntryNode`` is not read via
  ``ZODBEntryStorage`` but from ZODB root directly.
  [rnix]

- Remove ``AsAttrAccess``, ``Nodespaces``, and ``Attributes`` behaviors from
  ``ZODBEntry``.
  [rnix]

- Add ``ZODBEntryStorage.attrs``. Returns attributes of related
  ``ZODBEntryNode``.
  [rnix]

- Add ``ZODBEntryNode.__getitem__``. Sets ``ZODBEntryNode.entry`` as parent
  on children to keep traversal and acquisition paths sane.
  [rnix]

- Access ``principal_roles`` when initializing nodes with ``ZODBPrincipalACL``
  behavior applied to avoid lazy creation. Needed to prevent ``_p_changed``
  being set on first access.
  [rnix]

- Do not remember ``principal_roles`` via ``instance_property`` decorator
  on ``ZODBEntryPrincipalACL`` to avoid ``ZODB.POSException.ConnectionStateError``
  errors.
  [rnix]

- Proper handling of ``ZODBEntry`` and ``ZODBEntryNode`` in ``zodb_path``.
  [rnix]

- Add ``include_entry`` attribute to ``CatalogAware`` behavior. Flag controls
  whether to index entry node in calatog.
  [rnix]

- Add ``entry`` property to ``ZODBEntryNode``.
  [rnix]

- Use ``pyramid_zodbconn`` instead of ``repoze.zodbconn``.
  [rnix]

- Set ``node.interfaces.IOrdered`` on ``cone.zodb.entry.ZODBEntry`` to fix
  ``treerepr``.
  [rnix]

- Python 3 compatibility.
  [rnix]

- Upgrade to ``cone.app`` 1.0b1.
  [rnix]


< 1.0
-----

- Initial work.
  [rnix]


License
=======

Copyright (c) 2011-2021, BlueDynamics Alliance, Austria
Copyright (c) 2021-2025, Cone Contributors
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this
  list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice, this
  list of conditions and the following disclaimer in the documentation and/or
  other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.