Nikhil Benesch b841dccc2c Properly handle mixed implicit and explicit joins ... Parse a query like SELECT * FROM a NATURAL JOIN b, c NATURAL JOIN d as the SQL specification requires, i.e.: from: [ TableReference { relation: TableFactor::Table("a"), joins: [Join { relation: TableFactor::Table("b"), join_operator: JoinOperator::Natural, }] }, TableReference { relation: TableFactor::Table("c"), joins: [Join { relation: TableFactor::Table("d"), join_operator: JoinOperator::Natural, }] } ] Previously we were parsing such queries as relation: TableFactor::Table("a"), joins: [ Join { relation: TableFactor::Table("b"), join_operator: JoinOperator::Natural, }, Join { relation: TableFactor::Table("c"), join_operator: JoinOperator::Implicit, }, Join { relation: TableFactor::Table("d"), join_operator: JoinOperator::Natural, }, ] which did not make the join hierarchy clear.		2019-06-10 11:11:25 -04:00
..
sqlparser_common.rs	Properly handle mixed implicit and explicit joins	2019-06-10 11:11:25 -04:00
sqlparser_mssql.rs	Properly handle mixed implicit and explicit joins	2019-06-10 11:11:25 -04:00
sqlparser_postgres.rs	Parse column constraints in any order	2019-06-08 12:13:55 -04:00