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
PLK is currently implemented to strictly follow the SQL99 spec, which does not define implicit type coercions between type families (e.g. comparing an int with a varchar without any casting). partiql/partiql-lang#97 clarifies that this is an implementation-defined behavior. We should consider making the implicit coercions configurable:
set of implicit coercion modes -- coercion_postgresql, coercion_sql, coercion_redshift or
alancai98
changed the title
[Feature Request] Implicit coercion modes between types
[Feature Request] Add implicit coercion modes between types
Feb 3, 2025
PLK is currently implemented to strictly follow the SQL99 spec, which does not define implicit type coercions between type families (e.g. comparing an int with a varchar without any casting). partiql/partiql-lang#97 clarifies that this is an implementation-defined behavior. We should consider making the implicit coercions configurable:
coercion_postgresql
,coercion_sql
,coercion_redshift
orCAST
s and make certain implicit like PostgreSQL's CREATE CAST -- https://www.postgresql.org/docs/current/sql-createcast.htmlThe text was updated successfully, but these errors were encountered: