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

[Bug]: Data set is reset after updating software via .exe resulting in data loss #267

Closed
3 tasks done
chaoyu1999 opened this issue Aug 29, 2022 · 6 comments
Closed
3 tasks done

Comments

@chaoyu1999
Copy link

Describe the bug

Data set is reset after updating software via .exe resulting in data loss.
image

To reproduce

  1. Go to ...
  2. Click on ...
  3. Scroll down to ..
  4. See error

Version

3.4.0

OS

windwos 10

Validations

@antonreshetov
Copy link
Member

I am not a Windows user, but in my opinion you can not store data in the application folder, because when you update this folder can be overwritten.

@github-actions
Copy link

Hello @chaoyu1999. Please describe in detail the sequence of actions that leads to the bug (skip it if it's already there). Add screenshots of errors from the console. If possible add a video. Issues marked with need reproduction will be closed if they have no activity within 3 days.

@chaoyu1999
Copy link
Author

I am not a Windows user, but in my opinion you can not store data in the application folder, because when you update this folder can be overwritten.

It is recommended to add a cloud synchronization function

@antonreshetov
Copy link
Member

@antonreshetov Have you read the documentation before?

@chaoyu1999
Copy link
Author

@antonreshetov你以前读过文档吗?

Sorry, I should have looked at the documentation first

@antonreshetov
Copy link
Member

I'm closing this Issue because this case is your responsibility. As I wrote earlier, you should not use the application folder as a place to store the database.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants