@sqlpm/types-ts - npm Package Compare versions

Comparing version 1.2.3 to 1.2.4

package.json

 {
   "name": "@sqlpm/types-ts",
-  "version": "1.2.3",
+  "version": "1.2.4",
   "description": "Types shared between packages in the @sqlpm mono-repo",
@@ -33,3 +33,3 @@ "keywords": [
   },
-  "gitHead": "8545cd3a9a80f63680c47f115f603a049d8ad0bb"
+  "gitHead": "278c4bd6c9a820a5e0039c2096e67ea6a85ce421"
 }

src/index.ts

@@ -154,2 +154,24 @@ /**
   platform: DatabasePlatform | DatabasePlatforms
+
+  /**
+   * When a value is provided, causes Sql package manager to create a new
+   * database within the same postgresql cluster using the active connection
+   * database. Sql package manager then points at the new database and applies
+   * the sql schema to that packages database. Rolling back the schema will
+   * also cause the database to be removed?
+   *
+   * **@example**
+   * pg_cron can only run in a single database.
+   * (see https://github.com/citusdata/pg_cron/issues/89)
+   * Setting `packageDatabase: 'pg_cron'` will cause the sql script in the
+   * pg_cron package to execute in that database along with any of the
+   * dependencies. A package that depends on pg_cron will still run it's
+   * sql in the active connection.
+   */
+  packageDatabase?: {
+    databaseName: string,
+    // deleteDbOnRollback?: boolean
+    // connection - optional. By default the active connection is used meaning
+    // the database will be created in the same cluster
+  }
 }
@@ -156,0 +178,0 @@

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

10190

increased by10.51%

Lines of code

259

increased by8.82%

No dependency changes