docs: migration guide #887
Merged
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
Add newtype wrappers that implement `SerializeRow`/`SerializeCql` if the type wrapped over implements `ValueList`/`Value`. It should be useful when migrating codebases to the new traits gradually so that objects from the unchanged code which only implement the old trait can be passed to the code which was already updated to the new traits.
piodul
force-pushed
the
migration-guide
branch
2 times, most recently
from
048363e to
db4a121
Compare
Lorak-mmk
requested changes
Dec 18, 2023
|
|
||
| ## Background | ||
|
|
||
| When executing a statement through the CQL protocol, values for the bind markers are sent in a serialized, untyped form. In order to implement a safer and more robust interface, drivers can the information returned after preparing a statement to check the type of the data provided by the user against the actual types of the bind markers. |
There was a problem hiding this comment.
drivers can the information - did you mean can use?
There was a problem hiding this comment.
Yes - thanks, corrected.
|
|
||
| If you send simple statements along with non-empty lists of values, the slowdown will be as follows: | ||
|
|
||
| - For `Session::query`, the driver will optionally prepare the statement before sending it, incurring an additional round-trip. |
There was a problem hiding this comment.
optionally? I think driver is always going to do it
There was a problem hiding this comment.
Hm, yeah, by optional I meant here that it only happens when there are values for the query, but I agree that it's more natural to omit "optional" given the "If you send simple statements..." sentence.
In 0.11, the serialization traits are reworked and some guidance will be needed to adapt the existing code to the new traits. Add a document which explains the reason behind the changes, potential issues to watch for and tools that should make migration easier.
piodul
force-pushed
the
migration-guide
branch
from
db4a121 to
1f66942
Compare
Lorak-mmk
approved these changes
Dec 18, 2023
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.
In 0.11, the serialization traits are reworked and some guidance will be needed to adapt the existing code to the new traits. A document is added which explains the reason behind the changes, potential issues to watch for and tools that should make migration easier.
Additionally, the
ValueListandValueListAdapterhelper types are introduced, which are then mentioned in the migration doc.Pre-review checklist
./docs/source/.Fixes:annotations to PR description.