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

Client-only initialization/provision/migration #977

Open
Craige opened this issue Mar 7, 2023 · 0 comments
Open

Client-only initialization/provision/migration #977

Craige opened this issue Mar 7, 2023 · 0 comments

Comments

@Craige
Copy link
Contributor

Craige commented Mar 7, 2023

Reading through the docs, I'm not sure if this is currently possible but wanted to check: is it possible to perform client-only initialization and migration (without hitting the remote server)? Perhaps by shipping snapshots (full schema, partial data) with my releases?

The intention here is to ship a product with optional sync functionality. I have designed my EFCore migrations around the target server database and would like to just let Dotmim handle the client so the schema is always in a sync-ready state if/when that switch is flipped on and pointed at a remote.

Alternatively, if I build a second set of EFCore migrations for the client database, would these two databases even sync properly when Dotmim is pointed at both the remote and client?

Please advise.

@Craige Craige changed the title Client-only initialization/migration Client-only initialization/provision/migration Mar 7, 2023
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

No branches or pull requests

1 participant