OpenConstructionERP v6.6.0

Changed

• Embedded PostgreSQL is now the only database. SQLite has been removed from both the application and the test suite. This finishes the move that began in version 6.0.0, when an in-process PostgreSQL became the default with no Docker and no setup. The translation-memory cache now lives in the main database instead of its own SQLite file, the cost-database importer loads straight into PostgreSQL, and the SQLite engine and the dual-dialect database machinery are gone. The app still boots its own PostgreSQL on first run under ~/.openestimate/pgdata, or you can point DATABASE_URL at any external PostgreSQL. The one-time import of a legacy SQLite database on upgrade still works. There is no longer a SQLite fallback to run on.

Fixed

• 3D models placed on the project map now render. The map tile builder was writing each model's per-feature metadata as inline arrays, but the 3D Tiles format wants those values stored in the binary buffer and referenced by index. The viewer could not read the inline shape, so it gave up on the whole model and the map stayed blank. The metadata is now written the way the spec expects, with a binary property table, so the geometry shows on the map as soon as a model is placed.
• Database migrations now record correctly on PostgreSQL through the standard alembic path. The version table that alembic keeps for itself was capped at 32 characters, which is shorter than some of this project's revision names, so a plain incremental upgrade could fail the moment it recorded one of them. That column is now wide enough. A couple of migrations also created a boolean column with an integer default, which PostgreSQL rejects, and a set of older downgrade steps assumed SQLite behaviour, where a failed statement is harmless; on PostgreSQL the same failure aborts the whole transaction. The boolean defaults are fixed, and those downgrade steps now drop tables and columns with the database's own cascade and if-exists handling, so a downgrade no longer aborts on PostgreSQL. The recent migrations are exercised by an upgrade and downgrade roundtrip test against a real PostgreSQL server. The normal install path was never affected, since it creates the schema directly from the models and stamps it at the latest version.

Full Changelog: v6.5.0...v6.6.0