What problem does it solve? Adding PostgreSQL as a supported platform to an existing Thinkwise Software Factory application requires porting every category of hand-written SQL — control procedures, calculated fields, prefilters, and domain default queries — while navigating PostgreSQL-specific validation errors, dialect differences, and API gaps that are easy to miss and expensive to debug. ## Core Features & Use Cases - Nine-category migration checklist: Inventories every type of hand-written SQL and configuration that needs porting, from custom control procedures to seed data scripts, with per-platform entity locations. - T-SQL to PostgreSQL dialect reference: Provides mechanical substitution tables plus structural rewrites for triggers (batch inserted/deleted to row-level NEW/OLD), cross-item shared state via session settings, identity retrieval with returning ... into, and IMMUTABLE function requirements for generated columns. - Known issues and workarounds: Documents live-verified API gaps such as read-only branch_rdbms_type, never-generated subroutine placeholders, OData truncation of long template fields, and MERGE/FK errors during large-scale generation. - Use Case: A user asks to add PostgreSQL support to an existing SQL Server-only Thinkwise model; the skill walks through enabling the platform, porting ~150 code objects in risk order, resolving domain/column name collisions, and verifying generated code before deployment. ## Quick Start Ask the assistant to add PostgreSQL as a supported platform to your existing Thinkwise Software Factory model and port all custom SQL logic.
