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

Mock database persistence #17

Open
B3rn475 opened this issue Mar 7, 2018 · 0 comments
Open

Mock database persistence #17

B3rn475 opened this issue Mar 7, 2018 · 0 comments

Comments

@B3rn475
Copy link
Owner

B3rn475 commented Mar 7, 2018

At the moment the mock database in the generated/emulated code is not persisted.
After each run of the code generator it is restored to the default value.

It could be interesting to store the latest version of the database and preserve it after a model change.

Open questions:

  1. Where should i store the database? (metadata field of the model?)
  2. Could be interesting to edit the database from the model editor?
  3. How can i share the database between the emulators? (check if they are consistent)
  4. If I'm sharing the database between the emulators, how should I manage out of sync code?
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

1 participant