You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since HugSQL uses named parameters starting with a colon :, it is considered as special HugSQL syntax. We specifically work around a common use case in Postgresql SQL for explicit type casts starting with double colons ::. However, there are more uses of the colon : in Postgresql and possibly other DBs. For instance, Postgresql array slicing syntax uses colons.
Instead of working around every possible use of colons across many flavors of SQL, HugSQL should support the escaping of the colon : with a backslash \.
\: will be interpreted as a : in SQL output \\ will be interpreted as a \ in SQL output
The text was updated successfully, but these errors were encountered:
Since HugSQL uses named parameters starting with a colon
:
, it is considered as special HugSQL syntax. We specifically work around a common use case in Postgresql SQL for explicit type casts starting with double colons::
. However, there are more uses of the colon:
in Postgresql and possibly other DBs. For instance, Postgresql array slicing syntax uses colons.Instead of working around every possible use of colons across many flavors of SQL, HugSQL should support the escaping of the colon
:
with a backslash\
.\:
will be interpreted as a:
in SQL output\\
will be interpreted as a\
in SQL outputThe text was updated successfully, but these errors were encountered: