fix: Use jwt_private.current_database_id() instead of querying metaschema_public.database

The server middleware already sets jwt.claims.database_id in pgSettings,
so jwt_private.current_database_id() is a cheap function call vs the
previous approach of querying metaschema_public.database on every request.

Author: pyramation

graphile/graphile-presigned-url-plugin/src/plugin.ts

@@ -54,15 +54,16 @@ function buildS3Key(contentHash: string): string {
 }
 
 /**
- * Resolve the database_id from the pgClient's current database.
- * This queries metaschema to find the database row for the current connection.
+ * Resolve the database_id from the JWT context.
+ * The server middleware sets jwt.claims.database_id, which is accessible
+ * via jwt_private.current_database_id() — a simple function call, no
+ * metaschema query needed.
  */
 async function resolveDatabaseId(pgClient: any): Promise<string | null> {
   const result = await pgClient.query(
-    `SELECT id FROM metaschema_public.database WHERE db_name = current_database() LIMIT 1`,
+    `SELECT jwt_private.current_database_id() AS id`,
   );
-  if (result.rows.length === 0) return null;
-  return result.rows[0].id;
+  return result.rows[0]?.id ?? null;
 }
 
 // --- Plugin factory ---