Skip to content

Commit 77de808

Browse files
andymadsontreysp
andauthored
Update docs/quickstart/cli.md
Co-authored-by: Trey Spiller <1831878+treysp@users.noreply.github.com>
1 parent e9e5889 commit 77de808

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/quickstart/cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,7 @@ Line 5 describes what environments the plan will affect when applied - a new `pr
169169

170170
Lines 7-11 of the output show that SQLMesh detected three new models relative to the current empty environment.
171171

172-
Lines 12-16 list each model that will be executed by the plan, along with the date intervals or refresh types. For both `full_model` and `seed_model`, it shows `[full refresh]`, while for `incremental_model` it shows a specific date range `[2020-01-01 - 2025-04-17]`. The incremental model date range begins from 2020-01-01 because that date is specified in the `start` property of its `MODEL` statement.
172+
Lines 12-16 list each model that will be executed by the plan, along with the date intervals or refresh types. For both `full_model` and `seed_model`, it shows `[full refresh]`, while for `incremental_model` it shows a specific date range `[2020-01-01 - 2025-04-17]`. The incremental model date range begins from 2020-01-01 because the `full` model kind always fully rebuilds its table.
173173

174174
The `seed_model` date range begins on the same day the plan was made because `SEED` models have no temporality associated with them other than whether they have been modified since the previous SQLMesh plan.
175175

0 commit comments

Comments
 (0)