Document queries and joins in YSQL - Doc6849 #7173
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
|
The doc on queries and joins (for the Explorer section of Yugabyte docs) is ready for review. |
jaki
reviewed
Feb 11, 2021
| @@ -34,29 +34,28 @@ The following `SELECT` statement clauses provide flexiblity and allow you to fin | |||
| - The `DISTINCT` operator allows you to select distinct rows. | |||
| - The `ORDER BY` clause lets you sort rows. | |||
| - The `WHERE` clause allows you to apply filters to rows. | |||
| - The `LIMIT` and `FETCH` clauses allow you to select a subset of rows from a table. | |||
| - The `LIMIT` clauses allow you to select a subset of rows from a table. | |||
There was a problem hiding this comment.
s/clauses allow/clause allows/
m-iancu
reviewed
Feb 16, 2021
| Since YSQL is case-sensitive (that is, it treats the same characters differently depending on whether they are uppercase and lowercase), it is important to use correct cases when forming queries. For example, a table called `Employees` would not be recognized as an `employees` table, even if that is what you mean. That is, if your database contains an `employees` table and you want to query it using the following statement, the query execution will result in an error: | ||
|
|
||
| ```sql | ||
| SELECT name FROM Employees; |
There was a problem hiding this comment.
As far as I know this section is not quite correct.
Identifiers are normalized to lowercase unless they are quoted.
So, for example:
yugabyte=# create table fOo(iD int PRIMARY KEY);
CREATE TABLE
yugabyte=# select Id from FoO; -- any capitalization works if unquoted
id
----
(0 rows)
yugabyte=# create table "bAr"("iD" int PRIMARY KEY);
CREATE TABLE
yugabyte=# select iD from bAr; -- no capitalization works because identifiers will let lowercased if unquoted
ERROR: relation "bar" does not exist
LINE 1: select iD from bAr;
^
yugabyte=# select "iD" from "bAr"; -- quoting with the same as the declared capitalization will work.
iD
----
(0 rows)
yugabyte=# \d
List of relations
Schema | Name | Type | Owner
--------+------+-------+----------
public | bAr | table | yugabyte
public | foo | table | yugabyte
(2 rows)
There was a problem hiding this comment.
Fixed this section
|
This PR has been "in review" for 7 days. If there are no other comments, then I'm going to merge it today. |
|
Discussed with Mihnea. Decided to publish the doc and then implement review comments via a new PR. |
polarweasel
pushed a commit
to lizayugabyte/yugabyte-db
that referenced
this pull request
Mar 9, 2021
* Added content to queries.md * Added content to queries.md * edits * edits * Added content to queries.md and edited _index.md * Changed section title * Implemented Karthik's review comments * Moved some sections; minor edits * Implemented review comments; misc edits * Implemented review comments
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.
No description provided.