Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't give a ridiculously high pouchdb version #9819

Merged
merged 1 commit into from
Jan 9, 2024
Merged

Conversation

riknoll
Copy link
Member

@riknoll riknoll commented Jan 9, 2024

I originally did this so that I wouldn't have to worry about accidentally giving too low a version, but this ends up bricking the old pouchdb database and making it inaccessible. 5 is the value that pouchDB uses internally.

@riknoll riknoll requested a review from a team January 9, 2024 20:07
@riknoll riknoll merged commit 785cd94 into master Jan 9, 2024
7 checks passed
@riknoll riknoll deleted the riknoll-patch-1 branch January 9, 2024 21:35
riknoll added a commit that referenced this pull request Jan 22, 2024
…#9824)

* Stop using PouchDB (#9810)

* migrate pouchDB without a dependency on pouchDB

* obliterate PouchDb

* copy extra info to current db

* fix copyToLegacyEditor

* don't delete projects from pouchdb

* Don't give a ridiculously high pouchdb version (#9819)

* fix pouch db migration edge cases (#9820)

* delete the _doc_id_rev when migrating entries (#9822)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants