mirror of
https://github.com/apache/datafusion-sqlparser-rs.git
synced 2025-08-31 11:17:23 +00:00
00662c03fb
The column list in `CREATE INDEX` now matches the style used elsewhere, e.g. in `TableConstraint`, which is to use spaces after commas. ```sql -- before: CREATE INDEX idx_name ON table_name (column1,column2,column3); -- after: CREATE INDEX idx_name ON table_name (column1, column2, column3); ``` When `CreateIndex` was added, there was no explanation for the lack of spaces, so I assume it was just author preference. But standard style in all documentation I've seen is to use spaces after commas (including [MSSQL]'s documentation of `INCLUDE`, which copied the no-spaces style when added). [MSSQL]: https://learn.microsoft.com/en-us/sql/t-sql/statements/create-index-transact-sql?view=sql-server-ver17#i-create-an-index-with-included-non-key-columns |
||
|---|---|---|
| .. | ||
| queries/tpch | ||
| test_utils | ||
| pretty_print.rs | ||
| sqlparser_bigquery.rs | ||
| sqlparser_clickhouse.rs | ||
| sqlparser_common.rs | ||
| sqlparser_custom_dialect.rs | ||
| sqlparser_databricks.rs | ||
| sqlparser_duckdb.rs | ||
| sqlparser_hive.rs | ||
| sqlparser_mssql.rs | ||
| sqlparser_mysql.rs | ||
| sqlparser_postgres.rs | ||
| sqlparser_redshift.rs | ||
| sqlparser_regression.rs | ||
| sqlparser_snowflake.rs | ||
| sqlparser_sqlite.rs | ||