You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Craige
changed the title
Client-only initialization/migration
Client-only initialization/provision/migration
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.
The text was updated successfully, but these errors were encountered: