Skip to content

Commit bdf07c9

Browse files
committed
update docs
1 parent 0b1d124 commit bdf07c9

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

docs/guides/configuration.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -567,8 +567,10 @@ To mitigate this, SQLMesh offers an alternative 'dev-only' mode for using VDE. I
567567

568568
As the name suggests, 'dev-only' mode means that VDE is applied only in development environments, while in production, model tables and views are updated directly, bypassing the virtual layer. This also means that physical tables in production will be created using the original, unversioned model names. Users will still benefit from VDE and data reuse across development environments.
569569

570-
Please note that enabling this mode means that all data inserted in development environments is used only for [preview](../concepts/plans.md#data-preview-for-forward-only-changes) and will **not** be reused in production.
570+
Please note the following tradeoffs when enabling this mode:
571571

572+
- All data inserted in development environments is used only for [preview](../concepts/plans.md#data-preview-for-forward-only-changes) and will **not** be reused in production
573+
- Reverting a model to a previous version will trigger a full rebuild (unless the model is forward-only), as there is no versioned physical table to revert to
572574

573575
!!! warning
574576
Switching the mode for an existing project will result in a complete rebuild of all models in the project. Refer to the [Table Migration Guide](./table_migration.md) to migrate existing tables without rebuilding them from scratch.

0 commit comments

Comments
 (0)