blog.ponyorm.orgPony ORM Releases

PONYORM.COM ER Diagram Editor DOCUMENTATION GITHUB REPO Pony ORM Release 0.7.17 Leave a reply Pony ORM 0.7.17 now supports Python 3.11 and discontinues support for Python versions earlier than 3.8. Support for Python 3.11 Python 3.11 introduced changes to its bytecode to speed up execution ( see Python 3.11 changes ). As a consequence, updates were required in the Pony bytecode decompiler. Dropping Support for Python 3.6 and 3.7 Starting with Pony ORM Release 0.7.17, we are discontinuing support for Python 3.6 and 3.7. Pony ORM now supports Python versions 3.8 through 3.11. Bug Fixes Fix #636 : nullable IntArray and StrArray issues. Corrected quoting of table aliases in MySQL DELETE queries. Fixed handling of default argument values in hybrid methods and functions. This entry was posted in Releases on September 26, 2023 by Alexey Malashkevich . Pony ORM Release 0.7.16 Leave a reply Hi all! We released Pony ORM 0.7.16 . This release includes: A long-awaited support of Python 3.10. A possibility to create shared-in memory SQLite databases that can be accessed from multiple threads Support of Python 3.10 Previous versions of PonyORM use Python parser module from Python 2.x to parse Python AST. The support of this module was dropped in Python 3.10. Because of this, Pony ORM switches to new ast module. With this change, the support of Python 2.7 and old versions of Python 3 was dropped, and the supported versions now are Python 3.6-Python 3.10 Shared in-memory SQLite databases Previously in-memory SQLite databases are created in Pony ORM by specifying ":memory:" string as a database filename. The database created this way cannot be used in multiple threads. Now it is possible to use ":sharedmemory:" string to create a database that can be accessed from multiple threads. Other changes Do not perform optimistic checks when deleting an object (it is OK if it was already deleted by concurrent transaction) Validation of int fields should take into account field size and check that the value is fit into the range More tests for hybrid methods added Fix incorrect assertion check `assert t is translator.` Fix aggregated query sum(x.field for x in previous_query) #594 : Use a clearly synthetic filename when compiling dynamic code to not confuse coverage.py Use DecompileError exception instead of AssertionError when a function cannot be decompiled This entry was posted in Releases on January 27, 2022 by Alexey Malashkevich . Pony ORM Release 0.7.12 Leave a reply Hi all, Recently we have worked with the CockroachDB team and today we are excited to release Pony ORM 0.7.12 with the CockroachDB support. CockroachDB is a cloud-native SQL database for building global, scalable cloud services that survive disasters”. Another exciting news is that we have added a full blown continuous integration support. Now you can see the result of the tests at the Pony ORM page: https://github.com/ponyorm/pony Bugfixes Also, there is a list of bugfixes: Fix translation of getting array items with negative indexes Fix string getitem translation for slices and negative indexes PostgreSQL DISTINCT bug fixed for queries with ORDER BY clause Fix date difference syntax in PostgreSQL Fix casting json to dobule in PostgreSQL Fix count by several columns in PostgreSQL Fix PostgreSQL MIN and MAX expressions on boolean columns Fix determination of interactive mode in PyCharm Fix column definition when sql_default is specified: DEFAULT should be before NOT NULL Relax checks on updating in-memory cache indexes (don’t throw CacheIndexError on valid cases) Fix deduplication logic for attribute values Join our Telegram group , in case you haven’t already. This entry was posted in Releases on February 4, 2020 by Alexey Malashkevich . Pony ORM Release 0.7.10 Leave a reply This release includes the following bugfixes: Python3.7 and PyPy decompiling fixes Fix reading NULL from Optional nullable array column Fix handling of empty arrays in queries #415 : error message typo #432 : PonyFlask – request object can trigger teardown_request without real request Fix GROUP CONCAT separator for MySQL If you use Python 3.7 or PyPy we strongly recommend to upgrade to this release. Join our Telegram group , in case you haven’t already. This entry was posted in Releases on April 20, 2019 by Alexey Malashkevich . Pony ORM Migrations Leave a reply When we have started developing Pony ORM, we set a goal of creating the most pythonic, easy to use and powerful object-relational mapper for Python. Now, when we are getting feedback from our users, we are happy to see that we have managed to do this. We are grateful for your feedback, you are awesome! It helps us making Pony even better. The most frequent request at the moment is database migrations. Pony ORM provides intuitive object-oriented interface to a database. We want our migrations to share the same paradigm – to be easy to use and powerful. Pony ORM describes database model in terms of entities and its relationships. For human beings working with such a model is easier rather than with tables in a relational database. For example, it allows easily describe many-to-many relationships. In a relational database one need to add an intermediate table for this, which adds complexity. This way, Pony allows working with a database at a higher level of abstraction. Previous attempts By this moment, we have made a couple of attempts to implement the migrations. The result of those attempts were not officially released, although they are available at GitHub. The reason was that we’ve found some flaws in those approaches and for us it is important to provide an easy to use and powerful migrations interface. Based on that experience, we figured a better way and hope this approach is free from the drawbacks of previous versions. Migrations workflow The workflow of Pony ORM migrations looks as following: The migration file describes the changes to be made in the database. In order to generate such a file, Pony compares the current models taken from the source code with the models generated by applying all previous migrations. The resulting file contains the descriptions both at the entity level and the database tables level. Entity level The modifications at the entity level are described using the list of operations such as AddEntity, RemoveEntity, AddAttrbute, AddRelation, RenameEntity, etc. After applying these operations, Pony gets a new state of entities. Database level The modifications at the database level are described using another list with the operations like AddTable, AddColumn, AddForeignKey, AddIndex, etc. These operations provide full control on database changes. At this level one can add the ExecSQL command, which is used for data migrations. In most cases the database operations will be generated automatically, but when necessary, the developer can add any arbitrary operation to this list. It might be useful for complex updates or in early releases of the migration feature. Later we will be adding more and more well known use cases so that Pony can do those migrations automatically. Advantages This approach perfectly matches with a typical software development workflow when adding new features happens in separate branches and then those branches are being merged into the main branch. Operations which describe the changes to be made makes the merging process very simple. Once we have the new migrations, developers will be able to easily switch to the new version if currently they use an old approach. We believe the new Pony ORM migrations will help developing applications even faster. This entry was posted in News on March 19, 2019 by Alexey Malashkevich . Pony ORM Release 0.7.9 Leave a reply This release includes the following bugfixes: Fix handling of empty arrays and empty lists in queries Fix reading optional nullable array columns from database Join our Telegram group , in case you haven’t already. This entry was posted in Releases on...