From d19252c7d2881f91074ff15d4ee2c406d0b3111a Mon Sep 17 00:00:00 2001 From: Dan Lynch Date: Tue, 17 Mar 2026 01:17:47 +0000 Subject: [PATCH] refactor(server): remove schema naming env var forwarding from pgSettings MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit These settings (constructive.simple_schema_names, constructive.schema_use_underscores) are now set at the database level via ALTER DATABASE SET during provision, so the server no longer needs to forward them from env vars. This keeps the server generic and open-source — schema naming strategy is a database-level concern, not a server configuration concern. --- graphql/server/src/middleware/graphile.ts | 9 --------- 1 file changed, 9 deletions(-) diff --git a/graphql/server/src/middleware/graphile.ts b/graphql/server/src/middleware/graphile.ts index a8225b182..ef1618c2f 100644 --- a/graphql/server/src/middleware/graphile.ts +++ b/graphql/server/src/middleware/graphile.ts @@ -153,15 +153,6 @@ const buildPreset = ( const req = (requestContext as { expressv4?: { req?: Request } })?.expressv4?.req; const context: Record = {}; - // Schema naming strategy settings (for local development). - // See constructive-db: get_available_schema_hash / create_schema_trigger. - if (process.env.CONSTRUCTIVE_SIMPLE_SCHEMA_NAMES) { - context['constructive.simple_schema_names'] = process.env.CONSTRUCTIVE_SIMPLE_SCHEMA_NAMES; - } - if (process.env.CONSTRUCTIVE_SCHEMA_USE_UNDERSCORES) { - context['constructive.schema_use_underscores'] = process.env.CONSTRUCTIVE_SCHEMA_USE_UNDERSCORES; - } - if (req) { if (req.databaseId) { context['jwt.claims.database_id'] = req.databaseId;