Uh oh!
There was an error while loading. Please reload this page.
Add support for PostgreSQL LOCK TABLE - #2273
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Ifeanyi Ubah <ify1992@yahoo.com>
Co-authored-by: Ifeanyi Ubah <ify1992@yahoo.com>
Uh oh!
There was an error while loading. Please reload this page.
PostgreSQL 14 added LOCK. This implements parsing support for that statement. Beyond the added tests, the following minimum reproducible example demonstrate's sqlparser's current failure to parse this statement:
Cargo.toml:
src/main.rs:
Then run with
cargo run.