Columns named after SQL keywords causes problems #31
Labels
bug
Something isn't working
query-level
Change related to query DSL. Includes changes to `Query` datatype and its internals.
Columns SQL keyword names like
drop
or backend-specificend
(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
The text was updated successfully, but these errors were encountered: