perfact-dbschematools 26.5.0__tar.gz

perfact_dbschematools-26.5.0/.gitea/workflows/check.yml

@@ -0,0 +1,60 @@
+name: Build Package
+on:
+  push:
+    branches:
+      - 'main'
+  pull_request: {}
+
+jobs:
+  build:
+    strategy:
+      matrix:
+        target: ['jammy', 'bookworm', 'trixie']
+    runs-on: perfact-build-${{ matrix.target }}
+    steps:
+    - name: Install SSH key
+      run: |
+        mkdir -p /home/build/.ssh
+        printf '%s' '${{ secrets.SSH_DEPLOYMENT_KEY }}' > /home/build/.ssh/id_rsa
+        printf '%s' '${{ secrets.KNOWN_HOSTS }}' > /home/build/.ssh/known_hosts
+        chmod 600 /home/build/.ssh/id_rsa
+
+    - name: Checkout Repository
+      uses: actions/checkout@v3
+    - name: Change owner of build output Folder
+      run: sudo chown build:build /workspace/DebianPackages/ && echo OK!
+
+    - name: Update NMU changelog
+      run: |
+        echo Setting environment Variables
+        export DEBFULLNAME=${{ github.actor }}
+        echo Debian Fullname: $DEBFULLNAME
+        export DEBEMAIL=${{ github.actor }}@perfact.de
+        echo Debian Email: $DEBEMAIL
+        debchange --nmu Automated build on commit: ${{ gitea.sha }}
+
+    - name: Update package sources
+      run: sudo apt update || true
+
+    - name: Install build dependencies
+      run: sudo apt build-dep -y .
+
+    - name: Build
+      run: dpkg-buildpackage
+
+    - name: Collect result files
+      run: |
+        rm -rf /workspace/outputs/${{ gitea.repository }}/${{ gitea.ref_name }}/${{ matrix.target }}/
+        mkdir -p /workspace/outputs/${{ gitea.repository }}/${{ gitea.ref_name }}/${{ matrix.target }}
+        cp /workspace/DebianPackages/*.buildinfo /workspace/outputs/${{ gitea.repository }}/${{ gitea.ref_name }}/${{ matrix.target }}/
+        cp /workspace/DebianPackages/*.changes /workspace/outputs/${{ gitea.repository }}/${{ gitea.ref_name }}/${{ matrix.target }}/
+        cp /workspace/DebianPackages/*.deb /workspace/outputs/${{ gitea.repository }}/${{ gitea.ref_name }}/${{ matrix.target }}/
+        cp /workspace/DebianPackages/*.dsc /workspace/outputs/${{ gitea.repository }}/${{ gitea.ref_name }}/${{ matrix.target }}/
+        cp /workspace/DebianPackages/*.tar.xz /workspace/outputs/${{ gitea.repository }}/${{ gitea.ref_name }}/${{ matrix.target }}/
+
+    - name: Output the result as artifact
+      uses: actions/upload-artifact@v3
+      with:
+        name: ${{ matrix.target }}
+        path: /workspace/outputs/${{ gitea.repository }}/${{ gitea.ref_name }}/${{ matrix.target }}/
+        overwrite: true

perfact_dbschematools-26.5.0/.gitea/workflows/publish.yml

@@ -0,0 +1,31 @@
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - "[0-9]*"
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+
+      - name: Install build dependencies
+        run: python -m pip install --upgrade build twine
+
+      - name: Build package
+        run: python -m build
+
+      - name: Publish to PyPI
+        env:
+          TWINE_USERNAME: __token__
+          TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
+        run: twine upload dist/*

perfact_dbschematools-26.5.0/.gitignore

@@ -0,0 +1,22 @@
+*.pyc
+*.swp
+perfact_dbschematools.egg-info
+venv*
+.tox
+.coverage
+__pycache__
+build
+dist
+.temp-venv
+.wheels
+debian/perfact-dbschematools
+debian/.debhelper
+debian/perfact-dbschematools.substvars
+debian/debhelper-build-stamp
+debian/files
+tags
+tags.lock
+tags.temp
+*.orig
+.pybuild
+*.debhelper

perfact_dbschematools-26.5.0/PKG-INFO

@@ -0,0 +1,110 @@
+Metadata-Version: 2.4
+Name: perfact-dbschematools
+Version: 26.5.0
+Summary: Tools for deploying necessary schema changes for a perfactema database
+Author: Viktor Dick
+Author-email: Viktor Dick <viktor.dick@perfact.de>
+License: GPL-2.0-or-later
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Topic :: Database
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: oyaml
+Requires-Dist: pglast
+Requires-Dist: psycopg2
+Requires-Dist: perfact-dbutils
+
+# PerFact DBSchemaTools
+
+Tools for deploying necessary schema changes for a perfactema database.
+
+It aims to gradually replace DatabaseModifications by a schema definition
+delivered in the form of yaml files in a file system structure, so we don't
+define the steps to perform to arrive at some required schema, but the target
+schema itself. It also allows introspecting the current database and checking
+which (additive) change are to be performed to arrive at the correct schema.
+
+The maintainers of this project are:
+
+- Alexander Rolfes <alexander.rolfes@perfact.de>
+- Ján Jockusch <jan.jockusch@perfact.de>
+- Viktor Dick <viktor.dick@perfact.de>
+
+## Technical details
+
+The DBSchemaTools come bundled with an executable `perfact-dbschema` which is
+available in `/usr/bin`. This allows several actions to be performed (check out
+`--help`):
+- `patch`: Compare the current DB against the definitions provided in the
+  schema definition paths and extend the current DB as required.
+- `add`: Adds an entity to a schema definition path
+- `dump`: Dumps the full database into a schema definition path. Currently only
+  for debugging.
+
+Additionally, a wrapper `perfact-dbschema-add` is provided with a `sudoers`
+file that allows the user `zope` to execute it as user `perfact` on a typical
+PerFact system. This is intended to be used by the table manager while we
+transition more and more functionality over.
+
+On a PerFact template system, the package `perfact-dbutils-zope4` additionally
+provides a wrapper `perfact-dbschema-patch`. This is also used by the
+`zodbsync` configuration to make sure that any code deployment runs through the
+three steps:
+1. Check the schema definitions as recognized by perfact-dbschematools and
+   execute them, before changing anything inside Zope.
+2. Play back `DatabaseModifications` and related paths, and trigger their
+   application.
+3. Play back any remaining code changes, i.e. the code that depends on the new
+   schema.
+
+A **schema definition path** is usually something like
+`/opt/perfact/dbutils-zoperepo/__schema__` or a similar path somewhere in
+`/var/lib/perfact/zodbsync/layers` for an activated layer package. It contains
+a folder structure mostly oriented along tables, containing YAML files (and in
+the future probably also other file formats, when we include function
+definitions) that describe the entities that we require to be present in the
+database.
+
+In preparation for a future situation where we can develop for multiple layers
+on the same system, the main executable `perfact-dbschema` requires the path to
+be explicitly named, making its arguments somewhat clumsy at times. Usually,
+you should not have to interact with it directly, relying on the table manager
+and on the wrapper `perfact-dbschema-patch` instead.
+
+## Usage from other packages
+
+As of version 26.2.0, `perfact-dbschematools` no longer uses a virtual
+environment and can therefore be imported in other Python packages. A package
+that deploys some schema definitions that it requires to be executed to run can
+therefore do something like this at startup:
+```
+from perfact.dbschematools import patch
+patch('/path/to/my/schema/definition', my_connection_string)
+```
+
+## Configuration
+
+The default configuration file `/etc/pefact/dbschematools/config.yml` currently
+only describes the database connection string.
+
+## FAQs
+
+**I tried deploying a code state that uses schema definitions and it failed**
+
+- Is `perfact-dbutils-zope4` up to date? If you deployed using the layer
+  package `perfact-zope-layers-complete`, the dependency should be set
+  correctly so the necessary versions are installed, but if you only deployed
+  using a `git` checkout, you will need to update the packages accordingly.
+- Does the configuration of `perfact-dbschematools` contain the correct
+  connection string?
+- If you skipped the failures and continued the deployment, but fixed the
+  cause, you can execute `perfact-dbschema-patch` to retry.
+- Afterwards, you want to retry applying the `DatabaseModifications`.
+
+**During development, a column I created should have a different type after all**
+
+- Edit the file in `__schema__/tables/<table>/columns/<column>.yml`
+- Execute `perfact-dbschema-patch`.
+- If the column can not be converted automatically due to completely different
+  types, you will need to first delete the column manually.

perfact_dbschematools-26.5.0/README.md

@@ -0,0 +1,93 @@
+# PerFact DBSchemaTools
+
+Tools for deploying necessary schema changes for a perfactema database.
+
+It aims to gradually replace DatabaseModifications by a schema definition
+delivered in the form of yaml files in a file system structure, so we don't
+define the steps to perform to arrive at some required schema, but the target
+schema itself. It also allows introspecting the current database and checking
+which (additive) change are to be performed to arrive at the correct schema.
+
+The maintainers of this project are:
+
+- Alexander Rolfes <alexander.rolfes@perfact.de>
+- Ján Jockusch <jan.jockusch@perfact.de>
+- Viktor Dick <viktor.dick@perfact.de>
+
+## Technical details
+
+The DBSchemaTools come bundled with an executable `perfact-dbschema` which is
+available in `/usr/bin`. This allows several actions to be performed (check out
+`--help`):
+- `patch`: Compare the current DB against the definitions provided in the
+  schema definition paths and extend the current DB as required.
+- `add`: Adds an entity to a schema definition path
+- `dump`: Dumps the full database into a schema definition path. Currently only
+  for debugging.
+
+Additionally, a wrapper `perfact-dbschema-add` is provided with a `sudoers`
+file that allows the user `zope` to execute it as user `perfact` on a typical
+PerFact system. This is intended to be used by the table manager while we
+transition more and more functionality over.
+
+On a PerFact template system, the package `perfact-dbutils-zope4` additionally
+provides a wrapper `perfact-dbschema-patch`. This is also used by the
+`zodbsync` configuration to make sure that any code deployment runs through the
+three steps:
+1. Check the schema definitions as recognized by perfact-dbschematools and
+   execute them, before changing anything inside Zope.
+2. Play back `DatabaseModifications` and related paths, and trigger their
+   application.
+3. Play back any remaining code changes, i.e. the code that depends on the new
+   schema.
+
+A **schema definition path** is usually something like
+`/opt/perfact/dbutils-zoperepo/__schema__` or a similar path somewhere in
+`/var/lib/perfact/zodbsync/layers` for an activated layer package. It contains
+a folder structure mostly oriented along tables, containing YAML files (and in
+the future probably also other file formats, when we include function
+definitions) that describe the entities that we require to be present in the
+database.
+
+In preparation for a future situation where we can develop for multiple layers
+on the same system, the main executable `perfact-dbschema` requires the path to
+be explicitly named, making its arguments somewhat clumsy at times. Usually,
+you should not have to interact with it directly, relying on the table manager
+and on the wrapper `perfact-dbschema-patch` instead.
+
+## Usage from other packages
+
+As of version 26.2.0, `perfact-dbschematools` no longer uses a virtual
+environment and can therefore be imported in other Python packages. A package
+that deploys some schema definitions that it requires to be executed to run can
+therefore do something like this at startup:
+```
+from perfact.dbschematools import patch
+patch('/path/to/my/schema/definition', my_connection_string)
+```
+
+## Configuration
+
+The default configuration file `/etc/pefact/dbschematools/config.yml` currently
+only describes the database connection string.
+
+## FAQs
+
+**I tried deploying a code state that uses schema definitions and it failed**
+
+- Is `perfact-dbutils-zope4` up to date? If you deployed using the layer
+  package `perfact-zope-layers-complete`, the dependency should be set
+  correctly so the necessary versions are installed, but if you only deployed
+  using a `git` checkout, you will need to update the packages accordingly.
+- Does the configuration of `perfact-dbschematools` contain the correct
+  connection string?
+- If you skipped the failures and continued the deployment, but fixed the
+  cause, you can execute `perfact-dbschema-patch` to retry.
+- Afterwards, you want to retry applying the `DatabaseModifications`.
+
+**During development, a column I created should have a different type after all**
+
+- Edit the file in `__schema__/tables/<table>/columns/<column>.yml`
+- Execute `perfact-dbschema-patch`.
+- If the column can not be converted automatically due to completely different
+  types, you will need to first delete the column manually.

perfact_dbschematools-26.5.0/bandit.yaml

@@ -0,0 +1,3 @@
+# FILE: bandit.yaml
+assert_used:
+  skips: ['*_test.py', '*test_*.py']

perfact_dbschematools-26.5.0/data/etc/perfact/dbschematools/config.yaml

@@ -0,0 +1,2 @@
+# Connection string for connecting to the local database
+connstr: dbname=perfactema user=zope application_name=dbschematools

perfact_dbschematools-26.5.0/data/etc/sudoers.d/perfact-dbschematools

@@ -0,0 +1 @@
+zope ALL=(perfact) NOPASSWD:/usr/bin/perfact-dbschema-add

perfact_dbschematools-26.5.0/data/usr/bin/perfact-dbschema-add

@@ -0,0 +1,16 @@
+#!/usr/bin/python3
+
+# Wrapper for "perfact-dbschema add" that checks for an allowed path - because
+# this is allowed to be called via sudo, we do not allow just any path to be
+# passed.
+
+import sys
+import subprocess as sp
+
+if __name__ == '__main__':
+    # For now, only the default path is allowed. We might want to read layer
+    # definitions once we allow creating code for different layers
+    if sys.argv[1] != '/opt/perfact/dbutils-zoperepo/__schema__':
+        raise ValueError("Path not allowed")
+    sp.run(['/usr/bin/perfact-dbschema', 'add']
+           + sys.argv[1:], check=True)

perfact_dbschematools-26.5.0/debian/changelog

@@ -0,0 +1,152 @@
+perfact-dbschematools (26.5.0) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Add workflow to publish to pypi
+  * Switch to using ruff
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Tue, 12 May 2026 08:54:47 +0200
+
+perfact-dbschematools (26.4.0) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Add support for view definitions
+
+  [ Dionyssios Stamatis ]
+  * Normalize definitions of column defaults
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Fri, 17 Apr 2026 12:37:22 +0200
+
+perfact-dbschematools (26.3.0) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Keep defaults if the schema def of a column does not say anything about it
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Thu, 26 Feb 2026 14:07:44 +0100
+
+perfact-dbschematools (26.2.1) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Fix setup.cfg, which is read by jammy, to p.e. include the script
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Wed, 18 Feb 2026 07:05:44 +0100
+
+perfact-dbschematools (26.2.0) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Update documentation
+
+  [ Alexander Rolfes ]
+  * Correctly determine package version on build
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Wed, 11 Feb 2026 15:37:13 +0100
+
+perfact-dbschematools (26.1.0) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Add tox workflow
+  * Convert to system-wide dist-package
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Sat, 07 Feb 2026 13:06:27 +0100
+
+perfact-dbschematools (26.0.2) unstable; urgency=medium
+
+  [ Dionyssios Stamatis ]
+  * Remove deprecated parameter from argparse
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Mon, 05 Jan 2026 12:39:35 +0100
+
+perfact-dbschematools (26.0.1) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Revert switch from virtualenv to real package - dependencies can not be
+    satisfied
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Mon, 05 Jan 2026 10:26:52 +0100
+
+perfact-dbschematools (26.0.0) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Avoid using virtualenv
+  * Always execute when calling patch, deprecating the --execute flag
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Mon, 05 Jan 2026 09:55:34 +0100
+
+perfact-dbschematools (25.3.0) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Fix applying patch where column default is to be removed
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Wed, 17 Dec 2025 08:29:50 +0100
+
+perfact-dbschematools (25.2.0) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Avoid unnecessary type changes for equivalent types
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Tue, 16 Dec 2025 15:44:51 +0100
+
+perfact-dbschematools (25.1.0) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Add tests
+  * Omit "null" as default for columns
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Sat, 13 Dec 2025 11:09:33 +0100
+
+perfact-dbschematools (25.0.0) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Improve API for columns:
+    - Default columns are implicitly assumed
+    - Column definitions are expected to be in {table}/columns/{column}.yml
+    instead of {table}/columns/{column}/def.yml
+  * Fix usage of logger outputs, avoiding deprecation warnings
+  * Fix dependency on psycopg, making this work for trixie
+  * Purge virtualenv before recreating it in postinst
+  * Return best-guess queries from "add" to apply the changes directly
+  * Add subcommand "dump" to store current schema
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Fri, 31 Oct 2025 13:26:37 +0100
+
+perfact-dbschematools (23.0.3+nmu1) UNRELEASED; urgency=medium
+
+  [ Alexander Rolfes ]
+  * Add dependency on python3-yaml 
+
+ -- Alexander Rolfes <alexander.rolfes@perfact.de>  Tue, 09 Sep 2025 08:22:34 +0200
+
+perfact-dbschematools (23.0.3) unstable; urgency=medium
+
+  [ Alexander Rolfes ]
+  * Include psycopg3 inside of the virtual env instead of relying on
+    a system package
+
+ -- Alexander Rolfes <alexander.rolfes@perfact.de>  Mon, 11 Aug 2025 16:51:29 +0200
+
+perfact-dbschematools (23.0.2) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Actually check that layer config files are files before trying to open
+    them.
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Fri, 25 Jul 2025 08:26:03 +0200
+
+perfact-dbschematools (23.0.1) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Only check regular files for layer configs
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Tue, 22 Jul 2025 09:40:05 +0200
+
+perfact-dbschematools (23.0.0) unstable; urgency=medium
+
+  [ Viktor Dick ]
+  * Use deprecated version spec in pyproject.toml for backwards compatibility
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Fri, 11 Jul 2025 14:11:38 +0200
+
+perfact-dbschematools (0.1) UNRELEASED; urgency=medium
+
+  * Initial release.
+
+ -- Viktor Dick <viktor.dick@perfact.de>  Fri, 30 May 2025 12:56:18 +0200

perfact_dbschematools-26.5.0/debian/control

@@ -0,0 +1,32 @@
+Source: perfact-dbschematools
+Section: unknown
+Priority: optional
+Maintainer: Viktor Dick <viktor.dick@perfact.de>
+Rules-Requires-Root: no
+Build-Depends:
+ debhelper-compat (= 13),
+ dh-python,
+ python3,
+ python3-venv,
+ pybuild-plugin-pyproject,
+ python3-setuptools-scm,
+Standards-Version: 4.6.2
+
+Package: perfact-dbschematools
+Architecture: all
+Depends:
+ ${misc:Depends},
+ ${python3:Depends},
+ python3,
+ python3-venv,
+ python3-yaml,
+ python3-pglast,
+ perfact-pyoyaml,
+ python3-perfact,
+ python3-perfact-dbutils,
+ python3-psycopg2,
+Conflicts:
+ perfact-dbutils-zope4 (<=26.0.0),
+Description: Tools for deploying database schema changes.
+ It aims to gradually replace DatabaseModifications by a schema definition
+ delivered in the form of yaml files in a file system structure.

perfact_dbschematools-26.5.0/debian/copyright

@@ -0,0 +1,13 @@
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+
+Files: *
+Copyright: 2002-2025, PerFact Innovation GmbH & Co. KG <info@perfact.de>
+License: GPL-2+
+
+License: GPL-2+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; version 2 dated June, 1991, or (at
+ your option) any later version.
+ On Debian systems, the complete text of version 2 of the GNU General
+ Public License can be found in '/usr/share/common-licenses/GPL-2'.

perfact_dbschematools-26.5.0/debian/perfact-dbschematools.install

@@ -0,0 +1 @@
+data/* /

perfact_dbschematools-26.5.0/debian/perfact-dbschematools.postinst

@@ -0,0 +1,19 @@
+#!/bin/bash
+#
+# Post-installation procedure.
+
+set -e
+
+case "$1" in
+    configure)
+        # Remove virtualenv from older version, not needed anymore
+        rm -rf /var/lib/perfact/dbschematools
+    ;;
+    abort-upgrade|abort-remove|abort-deconfigure)
+    ;;
+
+    *)
+        echo "postinst called with unknown argument '$1'" >&2
+        exit 1
+    ;;
+esac

perfact_dbschematools-26.5.0/debian/rules

@@ -0,0 +1,11 @@
+#!/usr/bin/make -f
+
+# See debhelper(7) (uncomment to enable).
+# Output every command that modifies files on the build system.
+#export DH_VERBOSE = 1
+
+override_dh_auto_test:
+	tox
+
+%:
+	dh $@ --with python3 --buildsystem=pybuild

perfact_dbschematools-26.5.0/debian/source/format

@@ -0,0 +1 @@
+3.0 (native)

perfact_dbschematools-26.5.0/perfact/dbschematools/__init__.py

@@ -0,0 +1,4 @@
+#!/usr/bin/python3
+from .main import patch
+
+__all__ = ["patch"]

perfact_dbschematools-26.5.0/perfact/dbschematools/assets/columns/chdefault.sql

@@ -0,0 +1,2 @@
+alter table {tablename}
+  alter column {colname} set default {coldefault};

perfact_dbschematools-26.5.0/perfact/dbschematools/assets/columns/chtype.sql

@@ -0,0 +1,2 @@
+alter table {tablename}
+  alter column {colname} type {coltype};

perfact_dbschematools-26.5.0/perfact/dbschematools/assets/columns/create.sql

@@ -0,0 +1,3 @@
+alter table {tablename} add column if not exists
+  {colname} {coltype}
+;

perfact_dbschematools-26.5.0/perfact/dbschematools/assets/columns/patch.sql

@@ -0,0 +1,27 @@
+do $$
+  declare
+    cur_type text;
+  begin
+    select
+      udt_name || coalesce('(' || character_maximum_length || ')', '')
+    into
+      cur_type
+    from information_schema.columns
+    where table_schema not in ('pg_catalog', 'information_schema', 'hist')
+      and table_name = '{tablename}'
+      and column_name = '{colname}'
+    ;
+
+    if cur_type is null then
+      -- Column does not exist yet
+      alter table {tablename} add column if not exists
+        {colname} {coltype}
+      ;
+    end if;
+
+    if cur_type::regtype != '{coltype}'::regtype then
+      alter table {tablename}
+        alter column {colname} type {coltype};
+    end if;
+  end
+$$;

perfact_dbschematools-26.5.0/perfact/dbschematools/assets/columns/patch_default.sql

@@ -0,0 +1,20 @@
+do $$
+  declare
+    cur_default text;
+  begin
+    select
+      column_default
+    into
+      cur_default
+    from information_schema.columns
+    where table_schema not in ('pg_catalog', 'information_schema', 'hist')
+      and table_name = '{tablename}'
+      and column_name = '{colname}'
+    ;
+
+    if cur_default is distinct from {coldefault_esc} then
+      alter table {tablename}
+        alter column {colname} set default {coldefault};
+    end if;
+  end
+$$;

perfact_dbschematools-26.5.0/perfact/dbschematools/assets/columns/read.sql

@@ -0,0 +1,21 @@
+select
+  table_name collate "POSIX" as tablename,
+  column_name collate "POSIX" as name,
+  udt_name || coalesce('(' || character_maximum_length || ')', '') as type,
+  column_default as default
+
+from information_schema.columns
+
+where table_schema not in ('pg_catalog', 'information_schema', 'hist')
+  -- only valid table names
+  and table_name ~ '^[a-z0-9]+$'
+  -- no hist tables
+  and table_name !~ 'hist$'
+  -- only columns from base tables, not views
+  and table_name in (
+    select table_name
+    from information_schema.tables
+    where table_type = 'BASE TABLE'
+    and table_schema not in ('pg_catalog', 'information_schema', 'hist')
+  )
+order by tablename, ordinal_position