Skip to content

Columns named after SQL keywords causes problems #31

Open
@Kamirus

Description

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" }

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingquery-levelChange related to query DSL. Includes changes to `Query` datatype and its internals.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions