Document imprecise date support in TICK syntax#407
Open
bluestreak01 wants to merge 1 commit intomainfrom
Open
Conversation
TICK expressions now accept month-level (YYYY-MM) and year-level (YYYY) dates, expanding them to all constituent days before applying suffixes. This replaces verbose bracket ranges like `2024-01-[01..31]` with concise `[2024-01]` shorthand. Updates the main TICK reference with grammar changes, a new "Imprecise dates" section, and refreshes examples across 5 secondary doc pages. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
🚀 Build success! Latest successful preview: https://preview-407--questdb-documentation.netlify.app/docs/ Commit SHA: c719fd1
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
[2024-01]), year-level ([2024]), month bracket ranges (2024-[01..03]), bare forms, mixed-precision lists, expansion order, and calendar handlingliteral_datenow defines three precision levels; quick reference table adds 4 new rows for month-level, year-level, month range, and mixed-precision lists2024-01-[01..31]patterns with concise[2024-01]shorthand across 5 secondary doc pages (where.md, date-time.md, exchange-calendars.md, timestamps-timezones.md, designated-timestamp.md)Invalid date: 00andInvalid date: 13for out-of-range month valuesFiles changed
documentation/query/operators/tick.mddocumentation/query/sql/where.mddocumentation/query/operators/date-time.mddocumentation/query/operators/exchange-calendars.mddocumentation/concepts/timestamps-timezones.mddocumentation/concepts/designated-timestamp.mdTest plan
yarn buildpasses without broken links or MDX errors#imprecise-dates,#bare-imprecise-dates,#optional-brackets-for-date-variables) resolve correctly🤖 Generated with Claude Code