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

Should we store the browser data in an SQLite data store? #170

Open
pradeeban opened this issue Jul 18, 2023 · 0 comments
Open

Should we store the browser data in an SQLite data store? #170

pradeeban opened this issue Jul 18, 2023 · 0 comments
Labels
question Further information is requested

Comments

@pradeeban
Copy link
Member

Just a question to discuss. Not a request for enhancement.

Currently, the status and opened studies are stored in the user’s browser cache and cookies.

Therefore, major breaking changes in concore editor require the user to clear the respective site data, to ensure previously cached data are not persisted, and to avoid a conflict in case of a major update in the look-n-feel of concore editor. (This did not occur recently. But during the GSoC 2022 times, it was spotted often).

We proposed an SQLite data store to replace the browser-based cookies to store the context and status of concore editor. This way, the users will not need to empty their cache whenever there are major breaking updates on the concore editor.

However, this issue is on hold since this issue is not reproducing now.

@pradeeban pradeeban added the question Further information is requested label Jul 18, 2023
@pradeeban pradeeban changed the title Should we store the browser data in NoSQL? Should we store the browser data in SQLite data store? Jul 19, 2023
@pradeeban pradeeban changed the title Should we store the browser data in SQLite data store? Should we store the browser data in an SQLite data store? Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant