Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: apache/datafusion-sqlparser-rs
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: cipherstash/datafusion-sqlparser-rs
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 2 commits
  • 6 files changed
  • 2 contributors

Commits on Jan 6, 2025

  1. Handle empty projection for pg

    @tobyhede @freshtonic
    tobyhede authored and freshtonic committed Jan 6, 2025
    Configuration menu
    Copy the full SHA
    a0476e5 View commit details
    Browse the repository at this point in the history

  2. Parse Postgres's LOCK TABLE statement 

    See: https://www.postgresql.org/docs/current/sql-lock.html

PG's full syntax for this statement is supported:

```
LOCK [ TABLE ] [ ONLY ] name [ * ] [, ...] [ IN lockmode MODE ] [ NOWAIT ]

where lockmode is one of:

    ACCESS SHARE | ROW SHARE | ROW EXCLUSIVE | SHARE UPDATE EXCLUSIVE
    | SHARE | SHARE ROW EXCLUSIVE | EXCLUSIVE | ACCESS EXCLUSIVE
```

MySQL and Postgres have support very different syntax for `LOCK TABLE`
and are implemented with a breaking change on the `Statement::LockTables
{ .. }` variant, turning the variant into one which accepts a
`LockTables` enum with variants for MySQL and Posgres.
    @freshtonic
    freshtonic committed Jan 6, 2025
    Configuration menu
    Copy the full SHA
    1066440 View commit details
    Browse the repository at this point in the history
Loading