docs: Consolidate timestamp documentation and add TICK syntax reference #340
Conversation
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
Comprehensive rewrite of timestamp-related documentation to create a cohesive learning path for new users. **New content:** - Add TICK interval syntax documentation (`/docs/query/operators/tick/`) for the new temporal interval features from PR #6674 **Major rewrites:** - `designated-timestamp.md`: Complete rewrite covering why it exists, performance impact, how it works, limitations, best practices, and troubleshooting - `timestamps-timezones.md`: Refocused on querying by local time using TICK syntax, with conversion functions as secondary - `interval-scan.md`: Slimmed down to focus on EXPLAIN verification and edge cases, removing redundancy with designated-timestamp - `date-time.md`: Simplified to recommend TICK syntax, kept BETWEEN and interval() for specific use cases **Discovery path improvements:** - `quick-start.mdx`: Added explanation of TIMESTAMP() clause and prominent link to Schema design - `create-database.md`: Replaced vague explanations with clear bullet points explaining each time-series feature **Other changes:** - Added TICK to sidebar under Operators - Added See also section to partitions.md - Fixed DEDUP UPSERT KEYS in quotes table example (added instrument_id) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
🚀 Build success! Latest successful preview: https://preview-340--questdb-documentation.netlify.app/docs/ Commit SHA: ca28080
|
Update links to match renamed/removed sections: - timestamps-timezones/#timestamps-in-questdb → removed section - designated-timestamp/#resolution → #timestamp-resolution - date-time/#in-timerange → #in-with-timestamp-intervals - date-time/#between-value1-and-value2 → #between--and Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Target 30-80M rows per partition instead of 1-100M - Adjust for column count (more columns = fewer rows) - Flip table to show data volume → recommended interval - Clarify trade-offs: syscall overhead vs out-of-order performance Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The `<1` text was being parsed as JSX syntax, causing build failure. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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.
Summary
Comprehensive rewrite of timestamp-related documentation to create a cohesive learning path for new users and document the new TICK interval syntax.
Key changes:
TIMESTAMP()clausePages changed
/docs/query/operators/tick//docs/concepts/designated-timestamp//docs/concepts/timestamps-timezones//docs/concepts/deep-dive/interval-scan//docs/query/operators/date-time//docs/getting-started/quick-start//docs/getting-started/create-database//docs/concepts/partitions/sidebars.jsNew user journey
Before: User sees
TIMESTAMP(ts)in quick-start with no explanation, has to find multiple pages to understand it.After:
TIMESTAMP()does and links to Schema designTest plan
🤖 Generated with Claude Code