The bundled libpq-query package is outdated, with no support for syntax introduced in Postgresql 14, 15, 16 or 17. The current version only supports syntax up to Postgresql 13, which is nearing the end of its release and support cycle.
E.g. the following table definition won't parse, even though this is legal syntax in Posgresql 16:
CREATE TABLE IF NOT EXISTS project_api (
id int GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
foo TEXT NOT NULL,
bar TEXT NULL,
UNIQUE NULLS NOT DISTINCT (foo, bar)
);The above triggers the error syntax error at or near "NULLS".
Upgrading to a current version of libpg-query has the added advantage that it now produces a cross-platform WASM object, removing the need to create separate releses for different platforms.
The bundled libpq-query package is outdated, with no support for syntax introduced in Postgresql 14, 15, 16 or 17. The current version only supports syntax up to Postgresql 13, which is nearing the end of its release and support cycle.
E.g. the following table definition won't parse, even though this is legal syntax in Posgresql 16:
The above triggers the error
syntax error at or near "NULLS".Upgrading to a current version of libpg-query has the added advantage that it now produces a cross-platform WASM object, removing the need to create separate releses for different platforms.