Skip to content
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

Columns named after SQL keywords causes problems #31

Open
Kamirus opened this issue Jan 17, 2020 · 0 comments
Open

Columns named after SQL keywords causes problems #31

Kamirus opened this issue Jan 17, 2020 · 0 comments
Labels
bug Something isn't working query-level Change related to query DSL. Includes changes to `Query` datatype and its internals.

Comments

@Kamirus
Copy link
Owner

Kamirus commented Jan 17, 2020

Columns SQL keyword names like drop or backend-specific end (for PG) may not work properly.

PG should handle these names for queries without problems but insert/update/delete won't work properly.

There is a workaround - one can define the second table with explicitly escaped column names as follows and use the second table for insert/update/delete only

table  Table ( end  Int )
table = Table { name: "table" }

table_quote  Table ( "\"end\""  Int )
table_quote = Table { name: "table" }
@Kamirus Kamirus added the bug Something isn't working label Jan 17, 2020
@Kamirus Kamirus added the query-level Change related to query DSL. Includes changes to `Query` datatype and its internals. label Feb 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working query-level Change related to query DSL. Includes changes to `Query` datatype and its internals.
Projects
None yet
Development

No branches or pull requests

1 participant