-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
INSERT diagram isn't intuitive #5396
Comments
It seems reasonable to me to present both the general form (the one currently presented) and then underneath in sub-sections expand the |
I agree with @knz ... We do this for a few other SQL statements (e.g. CREATE TABLE, with "Basic" and "Expanded" diagrams) |
The |
In fact, it is. The full generality of selection queries is available to INSERT -- this is a pg feature, which MySQL does not have. Conversely all 3 selection clauses (TABLE, VALUES and SELECT) are valid top-level statements. |
You are right. I didn't know that. Everything is good then. |
Not sure if we'll have the bandwidth to update this for 19.2, so putting under 20.1. |
We have marked this issue as stale because it has been inactive for |
Jesse Seldess (jseldess) commented:
On Slack, @darinpp mentioned:
I think the diagram using
select_stmt
to represent various types of “selection clauses", includingVALUES
. The link to https://www.cockroachlabs.com/docs/stable/selection-queries.html in theselect_stmt
parameter description suggests as much.However, I very much agree with @darinpp that the diagram isn't friendly or intuitive. It should help users understand the statement syntax, as they most often use it, without having to dig deep and bounce around. We should revisit this and find a way to make the diagram express the most common cases, including
VALUES
.cc: @knz, who was involved in the way we documented "selection clauses". @rmloveland, @ericharmeling, not sure which of you wants to take this. Not sure if this is p1 or p2.
Jira Issue: DOC-322
The text was updated successfully, but these errors were encountered: