mirror/sqlstyle.guide
1
0
Fork 0
mirror of https://github.com/treffynnon/sqlstyle.guide.git synced 2025-03-09 12:49:51 -05:00
Code Activity

Merge pull request from emlazzarin/gh-pages

Browse source 
Fix a typo and some dangling spaces.
This commit is contained in:
Simon Holywell 2017-12-07 16:44:53 +10:00 committed by GitHub
commit ad249d15d3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions

6
_includes/sqlstyle.guide.md
View file

@ -273,7 +273,7 @@ SELECT r.last_name
Subqueries should also be aligned to the right side of the river and then laid
out using the same style as any other query. Sometimes it will make sense to have
the closing parenthesis on a new line at the same character position as it's
the closing parenthesis on a new line at the same character position as its
opening partner—this is especially true where you have nested subqueries.
```sql
@ -343,7 +343,7 @@ about though so it is important that a standard set of guidelines are followed.
#### Choosing keys
Deciding the column(s) that will form the keys in the definition should be a
Deciding the column(s) that will form the keys in the definition should be a
carefully considered activity as it will effect performance and data integrity.
1. The key should be unique to some degree.
@ -1276,7 +1276,7 @@ ZONE
[rivers]: http://practicaltypography.com/one-space-between-sentences.html
"Practical Typography: one space between sentences"
[reserved-keywords]: #reserved-keyword-reference
"Reserved keyword reference"
"Reserved keyword reference"
[eav]: https://en.wikipedia.org/wiki/Entity%E2%80%93attribute%E2%80%93value_model
"Wikipedia: Entity–attribute–value model"
[sqlstyleguide]: http://www.sqlstyle.guide