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
For some historical reason, the default schema is "wasg2" even for PostgreSQL databases. This causes checks to scan this schema instead of expected "public" when searching for metadata. When the <schema>public</schema> is explicitly set, the checks work as inteneded.
For example my failing check was for the column <check type="column" name="content" table="internal_note" inverted="true" />
which caused the alter to be skipped even if the column did exist.
The text was updated successfully, but these errors were encountered:
For some historical reason, the default schema is "wasg2" even for PostgreSQL databases. This causes checks to scan this schema instead of expected "public" when searching for metadata. When the
<schema>public</schema>
is explicitly set, the checks work as inteneded.For example my failing check was for the column
<check type="column" name="content" table="internal_note" inverted="true" />
which caused the alter to be skipped even if the column did exist.
The text was updated successfully, but these errors were encountered: