Release 0.9.3#544
Merged
Merged
Conversation
Contributor
Author
|
@abondar Could you take a look at this release PR when you have a chance? It would be great to publish a new version so users can use Aerich with Tortoise ORM 1.0+. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For tortoise 1.0+, you can use the builtin migration commands instead of aerich. See more at: https://tortoise.github.io/migration.html
Added
[tool.tortoise]section when running aerich init with tortoise 1.0+ (#536)Changed
on_delete(#511)Fixed
init-dbnow checks theaerichtable in the database (not the migrations folder) to detect prior initialization, so it works correctly on a fresh database that already has migration files (e.g. cloned from a repository) (#526)aerich<=0.9.1(noMODELS_STATEsection). Online commands can still read state from theaerichtable;aerich migratewarns only when it creates a new migration file, and offline migration still requiresaerich fix-migrations. Set the env varAERICH_NO_OLD_FORMAT_WARNING=1to silence the warning (#542)inspectdboutputUnicodeEncodeErroron Windows when database comments contain characters outside the system encoding (e.g. GBK) (#543)Full Changelog: v0.9.2...dev