[OneBot] Migrating to Realm #752
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
DarkRRb
requested review from
Executor-Cheng,
Linwenxuan04,
CrackTC,
Decrabbityyy,
ishkong,
KusaGumina,
pk5ls20 and
sisi0318
pk5ls20
approved these changes
Feb 4, 2025
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.
WARNING: BREAKING CHANGE
You can use DatabaseShift to migrate LiteDB database files to Realm.
To developers
When modifying the MessageRecord, you must increment the
SchemaVersion. Beyond simply adding or removing fields (Realm will automatically assign default values, but if complex processing is required, you must also implement the migration logic in theMigrationCallback), you should add migration logic in theMigrationCallbackto handle transitions from all previous schema versions to the current version.