Skip to content

Commit b28dd82

Browse files
authored
Merge pull request #172 from nickolay/pr/readme
documentation updates
2 parents 98f97d0 + 1cf9e5e commit b28dd82

File tree

2 files changed

+7
-8
lines changed

2 files changed

+7
-8
lines changed

CHANGELOG.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ Check https://github.com/andygrove/sqlparser-rs/commits/master for undocumented
1414

1515
### Added
1616
- Support basic forms of `CREATE INDEX` and `DROP INDEX` (#167) - thanks @mashuai!
17+
- Support `ON { UPDATE | DELETE } { RESTRICT | CASCADE | SET NULL | NO ACTION | SET DEFAULT }` in `FOREIGN KEY` constraints (#170) - thanks @c7hm4r!
1718
- Support MSSQL `TOP (<N>) [ PERCENT ] [ WITH TIES ]` (#150) - thanks @alexkyllo!
1819
- Support MySQL `LIMIT row_count OFFSET offset` (not followed by `ROW` or `ROWS`) and remember which variant was parsed (#158) - thanks @mjibson!
1920
- Support PostgreSQL `CREATE TABLE IF NOT EXISTS table_name` (#163) - thanks @alex-dukhno!

README.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -46,11 +46,9 @@ SQL was first standardized in 1987, and revisions of the standard have been
4646
published regularly since. Most revisions have added significant new features to
4747
the language, and as a result no database claims to support the full breadth of
4848
features. This parser currently supports most of the SQL-92 syntax, plus some
49-
syntax from newer versions that have been explicitly requested, plus some MSSQL-
50-
and PostgreSQL-specific syntax. Whenever possible, the [online SQL:2011
51-
grammar][sql-2011-grammar] is used to guide what syntax to accept. (We will
52-
happily accept changes that conform to the SQL:2016 syntax as well, but that
53-
edition's grammar is not yet available online.)
49+
syntax from newer versions that have been explicitly requested, plus some MSSQL,
50+
PostgreSQL, and other dialect-specific syntax. Whenever possible, the [online
51+
SQL:2016 grammar][sql-2016-grammar] is used to guide what syntax to accept.
5452

5553
Unfortunately, stating anything more specific about compliance is difficult.
5654
There is no publicly available test suite that can assess compliance
@@ -105,8 +103,8 @@ If you are unable to submit a patch, feel free to file an issue instead. Please
105103
try to include:
106104

107105
* some representative examples of the syntax you wish to support or fix;
108-
* the relevant bits of the [SQL grammar][sql-2011-grammar], if the syntax is
109-
part of SQL:2011; and
106+
* the relevant bits of the [SQL grammar][sql-2016-grammar], if the syntax is
107+
part of SQL:2016; and
110108
* links to documentation for the feature for a few of the most popular
111109
databases that support it.
112110

@@ -123,5 +121,5 @@ resources.
123121
[DataFusion]: https://github.com/apache/arrow/tree/master/rust/datafusion
124122
[LocustDB]: https://github.com/cswinter/LocustDB
125123
[Pratt Parser]: https://tdop.github.io/
126-
[sql-2011-grammar]: https://jakewheat.github.io/sql-overview/sql-2011-foundation-grammar.html
124+
[sql-2016-grammar]: https://jakewheat.github.io/sql-overview/sql-2016-foundation-grammar.html
127125
[sql-standard]: https://en.wikipedia.org/wiki/ISO/IEC_9075

0 commit comments

Comments
 (0)