Releases: polypheny/PolyNOM
v0.3.2
v0.3.1
Highlights
Per-application statement logs
- Logging now captures all committed data and schema-modifying statements on a per-application basis.
- Provides improved visibility into database activity and can serve as a foundation for replication and recovery mechanisms.
Statement objects available to users
- Statement objects can now be created and executed directly within a session.
- This makes query execution more explicit and integrates seamlessly with the new logging functionality.
- The previous
Session.execute(...)method has been deprecated and will be removed in a future release.
Documentation improvements
Extended coverage now includes:
- Querying
- Statement objects
- Flex models
- Logging features
Deprecations
session._execute(language: str, statement: str, parameters=None, namespace: str=None, fetch: bool=True)is deprecated.- Users should migrate to using statement objects executed within a session.
- The new method is
session._execute(statement: Statement, fetch=True). - The deprecated method will be removed in a future release.
v0.2.0
This release focuses on enhancing ease of use and developer experience by introducing the following:
-
Dump and Load Functionality: A new mechanism has been introduced to dump and load application-related data. This simplifies data migration, backups, and sharing across environments.
-
Improved Foreign Key Field Signatures: Method signatures for foreign key fields have been refined to reduce the risk of misconfiguration when specifying referenced entities and fields.
-
Extended Documentation: The documentation has been expanded with new sections that provide broader coverage of the framework’s features, along with practical examples to help users get started quickly and use features correctly.
These improvements aim to make the framework more intuitive and less error-prone for developers.
v0.1.0
Initial release of PolyNOM providing basic features.