Skip to content

cannot use CURRENT_TIMESTAMP in sqlite #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
lovasoa opened this issue Jul 14, 2023 · 1 comment
Closed

cannot use CURRENT_TIMESTAMP in sqlite #31

lovasoa opened this issue Jul 14, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@lovasoa
Copy link
Collaborator

lovasoa commented Jul 14, 2023

See apache/datafusion-sqlparser-rs#918

The simplest workaround is to use date('now') instead.

@lovasoa lovasoa added the bug Something isn't working label Jul 14, 2023
@lovasoa
Copy link
Collaborator Author

lovasoa commented Jul 30, 2023

lovasoa added a commit that referenced this issue Nov 5, 2023
fixes #31 (cannot use CURRENT_TIMESTAMP in sqlite)
fixes transaction handling on databases with a "BEGIN TRANSACTION" syntax (instead of START TRANSACTION) such as SQLite

See https://github.com/sqlparser-rs/sqlparser-rs/blob/main/CHANGELOG.md#0370-2023-08-22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant