add context about updated_at support #6746
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this pr adds what type the updated_at field of the timestamp strategy should have in relation to iso date strings and unix epoch integers. Resolves # #1948
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
nataliefiann
reviewed
Jan 9, 2025
website/docs/docs/build/snapshots.md
Outdated
| @@ -80,7 +80,7 @@ The following table outlines the configurations available for snapshots: | |||
| | [strategy](/reference/resource-configs/strategy) | The snapshot strategy to use. Valid values: `timestamp` or `check` | Yes | timestamp | | |||
| | [unique_key](/reference/resource-configs/unique_key) | A <Term id="primary-key" /> column(s) (string or array) or expression for the record | Yes | `id` or `[order_id, product_id]` | | |||
| | [check_cols](/reference/resource-configs/check_cols) | If using the `check` strategy, then the columns to check | Only if using the `check` strategy | ["status"] | | |||
| | [updated_at](/reference/resource-configs/updated_at) | If using the `timestamp` strategy, the timestamp column to compare | Only if using the `timestamp` strategy | updated_at | | |||
| | [updated_at](/reference/resource-configs/updated_at) | If using the `timestamp` strategy, the timestamp column to compare. May support ISO date strings and unix epoch integers, depending on the data platform you use. | Only if using the `timestamp` strategy | updated_at | | |||
There was a problem hiding this comment.
Hiya @mirnawong1
This reads a bit funny to me. Should this read: "If using the timestamp strategy, the timestamp column will compare?"
Kind Regards
There was a problem hiding this comment.
eek that does read weird! how about:
A column in your snapshot query results that indicates when each record was last updated, used in the timestamp strategy.
mirnawong1
commented
Jan 9, 2025
mirnawong1
commented
Jan 9, 2025
nataliefiann
approved these changes
Jan 9, 2025
There was a problem hiding this comment.
Hiya @mirnawong1
Thanks for creating this PR. I've approved this for you and left a question.
Kind Regards
Natalie
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this pr adds what type the updated_at field of the timestamp strategy should have in relation to iso date strings and unix epoch integers.
Resolves # #1948
🚀 Deployment available! Here are the direct links to the updated files: