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
COMMENT ON is supported in #266, but not for EXTENSION.
I wouldn't mind if the comments end up getting dropped, just as long as the SQL gets parsed- in that case a workaround is to filter the comment out of the schema.sql before it gets to sqldef.
psqldef ... <<< $(grep -v 'COMMENT ON EXTENSION' schema.sql)
Platform
OS: macOS (probably all)
RDBMS: PostgreSQL
Version: v0.15.12
--export output
Input SQL
CREATE EXTENSION IF NOT EXISTS pg_stat_statements WITH SCHEMA public;
COMMENT ON EXTENSION pg_stat_statements IS 'track execution statistics of all SQL statements executed';
CREATE EXTENSION IF NOT EXISTS pgcrypto WITH SCHEMA public;
COMMENT ON EXTENSION pgcrypto IS 'cryptographic functions';
Current output
found syntax error when parsing DDL "COMMENT ON EXTENSION ...
Expected output
None compared to the above
The text was updated successfully, but these errors were encountered:
It's not clear to me from that change where the parser is actually failing and would need to be modified. I am content to just use my workaround since none of the extension comments I see seem useful.
Overview
COMMENT ON
is supported in #266, but not forEXTENSION
.I wouldn't mind if the comments end up getting dropped, just as long as the SQL gets parsed- in that case a workaround is to filter the comment out of the schema.sql before it gets to sqldef.
Platform
--export output
Input SQL
Current output
Expected output
None compared to the above
The text was updated successfully, but these errors were encountered: