Quick question, and also maybe a feature request.
Right now (unless I’m missing something), moving data from dev to prod feels very all or nothing:
-
Either all your dev data comes over
-
Or nothing does
That puts you in a weird spot where you either:
-
Keep dev totally clean all the time, or
-
Rebuild a bunch of stuff manually in prod after deploys
That works for some tables, but not others.
Examples:
-
Config-type tables (dropdown values, statuses, categories, etc.)
It’d be awesome if this data could come over automatically so you don’t have to re-create it by hand. -
User-generated tables (notes, tickets, comments, etc.)
These should usually stay empty in prod and never get overwritten. -
Edge cases
Sometimes you just want to add new rows from dev without touching what already exists in prod.
Ideal world:
-
On each snapshot/deploy you could choose:
-
Bring everything
-
Bring nothing
-
Or manage it table-by-table
-
-
Per table options like:
-
Replace
-
Ignore
-
Append only (add new rows, don’t overwrite)
-
If there’s already a workaround for this, please let me know!
If not, this would make dev → prod workflows way smoother for real apps.
Curious if others have hit this too.