docs: add LATERAL derived tables documentation#22583
docs: add LATERAL derived tables documentation#22583terry1purcell wants to merge 9 commits intopingcap:masterfrom
Conversation
Document the LATERAL derived table syntax support added in pingcap/tidb#67076. Includes a new page with syntax, examples, and current limitations, plus updates to mysql-compatibility.md and TOC.md. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces comprehensive documentation for LATERAL derived tables in TiDB. It provides users with detailed information on this SQL feature, including its syntax, practical examples, and current implementation status, ensuring clarity on its compatibility with MySQL and TiDB's roadmap for full support. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces new documentation for LATERAL Derived Tables in TiDB, including a dedicated markdown file explaining its concept, syntax, examples, and current support status (parsing only, execution pending). The changes also update the table of contents and the MySQL compatibility document to reference this new content. Review feedback suggests minor stylistic and clarity improvements for the new documentation, such as rephrasing for active voice and better wording for column descriptions.
LATERAL was added as a reserved keyword in pingcap/tidb#67076. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
qiancai
left a comment
There was a problem hiding this comment.
A few line-level doc fixes are still needed before merge.
|
@terry1purcell Please involve a tech reviewer for this doc PRs. Thanks. |
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Document the LATERAL derived table syntax support added in pingcap/tidb#67076. Includes a new page with syntax, examples, and current limitations, plus updates to mysql-compatibility.md and TOC.md.
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?