Documentation: Add section about migration from crate.client
#135
Conversation
This file contains 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
amotl
requested review from
matriv,
surister,
simonprickett and
seut
and removed request for
matriv and
surister
surister
approved these changes
Jun 17, 2024
simonprickett
approved these changes
Jun 17, 2024
Co-authored-by: Simon Prickett <simon@crudworks.org>
amotl
force-pushed
the
amo/migration-docs
branch
from
d09afd5 to
a7b0093
Compare
|
Thanks! |
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.
Introduction
In June 2024, code from the package crate[sqlalchemy] has been transferred to the package sqlalchemy-cratedb. For 80% of the use cases, this will be a drop-in replacement with no noticeable changes.
About
This patch adds a corresponding documentation section conveying a few migration notes.
Preview
https://sqlalchemy-cratedb--135.org.readthedocs.build/migrate-from-crate-client.html
Trivia
Happy to receive an acknowledgement from anyone, to be able to continue work depending on this. Thanks!
/cc @surister, @matriv