Initial assessment of a port to LiteDB 5 #51
Closed
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
|
Hello there @TeaDrivenDev, what is the current status of this at the moment? Do you plan on continuing the work for the latest version upgrade or you want to leave it so that someone else picks it up? |
|
Implemented by #61 |
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.
As noted in #45, LiteDB.FSharp is currently incompatible with LiteDB 5.x due to API changes. These changes are significant in certain areas (especially the query API) and will require more in-depth knowledge and research in order to make LiteDB.FSharp compatible with the new version of LiteDB.
I do not have the LiteDB experience to handle those more complex changes, but I have made the simple ones to fix individual compile errors. (Those changes have been made naively and do not necessarily have to be correct.) I have marked all the places that I could not get to compile with
TODOcomments.I have no immediate plans to pursue this further, as I don't know how; this is intended more as a jumping-off point, so someone else doesn't have to start from scratch.