@prisma/orm-postgres 8.0.0-rc.13-dev.9 → 8.0.0-rc.13-dev.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -15,6 +15,8 @@ The one package a PostgreSQL application installs. It wires the framework, the S
15
15
  └── @prisma/orm-toolchain ORM command family for the `prisma` CLI, emitter, config loader
16
16
  ```
17
17
 
18
+ `temporal-polyfill` is a required peer dependency. The control plane, such as the `prisma` commands and the Vite plugin, loads it as a fallback `Temporal` when the runtime has none, and a project that already installs it for its own code has one copy. npm, pnpm and bun install it automatically; with Yarn, add `temporal-polyfill` to your dependencies.
19
+
18
20
  ## Entrypoints
19
21
 
20
22
  | Namespace | Surface |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@prisma/orm-postgres",
3
- "version": "8.0.0-rc.13-dev.9",
3
+ "version": "8.0.0-rc.13-dev.11",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "sideEffects": false,
@@ -10,10 +10,10 @@
10
10
  "skills"
11
11
  ],
12
12
  "dependencies": {
13
- "@prisma/orm-family-sql": "8.0.0-rc.13-dev.9",
14
- "@prisma/orm-framework": "8.0.0-rc.13-dev.9",
15
- "@prisma/orm-target-postgres": "8.0.0-rc.13-dev.9",
16
- "@prisma/orm-toolchain": "8.0.0-rc.13-dev.9",
13
+ "@prisma/orm-family-sql": "8.0.0-rc.13-dev.11",
14
+ "@prisma/orm-framework": "8.0.0-rc.13-dev.11",
15
+ "@prisma/orm-target-postgres": "8.0.0-rc.13-dev.11",
16
+ "@prisma/orm-toolchain": "8.0.0-rc.13-dev.11",
17
17
  "@types/node": "26.1.2",
18
18
  "@types/pg": "8.20.4",
19
19
  "arktype": "^2.2.2",
@@ -22,13 +22,14 @@
22
22
  "tinyglobby": "^0.2.17"
23
23
  },
24
24
  "devDependencies": {
25
- "@internal/postgres": "8.0.0-rc.13-dev.9",
26
- "@repo/tsconfig": "8.0.0-rc.13-dev.9",
27
- "@repo/tsdown": "8.0.0-rc.13-dev.9",
25
+ "@internal/postgres": "8.0.0-rc.13-dev.11",
26
+ "@repo/tsconfig": "8.0.0-rc.13-dev.11",
27
+ "@repo/tsdown": "8.0.0-rc.13-dev.11",
28
28
  "tsdown": "0.22.14",
29
29
  "typescript": "5.9.3"
30
30
  },
31
31
  "peerDependencies": {
32
+ "temporal-polyfill": "^1.0.4",
32
33
  "typescript": ">=5.9"
33
34
  },
34
35
  "peerDependenciesMeta": {
@@ -15,7 +15,7 @@ description: >-
15
15
  ORM 7 or earlier (schema.prisma + @prisma/client).
16
16
  metadata:
17
17
  library: '@prisma/orm-postgres'
18
- library_version: '8.0.0-rc.13-dev.9'
18
+ library_version: '8.0.0-rc.13-dev.11'
19
19
  version: '2026-09-12'
20
20
  ---
21
21
 
@@ -116,7 +116,7 @@ model Post {
116
116
 
117
117
  Then run `pnpm prisma contract emit` (or rely on the Vite plugin — see `references/build.md`). Specify cascade behaviour explicitly with `onDelete` / `onUpdate`; the default is `Restrict`.
118
118
 
119
- **Temporal columns.** On PostgreSQL, `Date`, `Timestamp(p)`, `Timestamptz(p)` and `Time(p)` read and write `Temporal` values (`Temporal.PlainDate`, `PlainDateTime`, `Instant`, `PlainTime`), never JavaScript `Date`. They need a global `Temporal` at query time: Node.js 26.8.2 and later ship `globalThis.Temporal`; 26.8.1 and earlier — including every 22 and 24 release — do not, and the first read or write of such a column throws `RUNTIME.TEMPORAL_UNAVAILABLE`. On those runtimes either `import 'temporal-polyfill/full/global'` before the first query (add `temporal-polyfill` as a dependency) or author the column as `DateString` / `TimestampString(p)` / `TimestamptzString(p)` / `TimeString(p)`, which carry PostgreSQL's own text and need no `Temporal`.
119
+ **Temporal columns.** On PostgreSQL, `Date`, `Timestamp(p)`, `Timestamptz(p)` and `Time(p)` read and write `Temporal` values (`Temporal.PlainDate`, `PlainDateTime`, `Instant`, `PlainTime`), never JavaScript `Date`. They need a global `Temporal` at query time: Node.js 26.8.2 and later ship `globalThis.Temporal`; 26.8.1 and earlier — including every 22 and 24 release — do not, and the first read or write of such a column throws `RUNTIME.TEMPORAL_UNAVAILABLE`. On those runtimes either `import 'temporal-polyfill/full/global'` before the first query (add `temporal-polyfill` as a dependency) or author the column as `DateString` / `TimestampString(p)` / `TimestamptzString(p)` / `TimeString(p)`, which carry PostgreSQL's own text and need no `Temporal`. `prisma contract emit`, `prisma db init` and the other commands need no global `Temporal`: the Postgres target loads `temporal-polyfill` as a fallback `Temporal` for the control plane, and sets no global. `temporal-polyfill` is a required peer dependency of `@prisma/orm-postgres`. npm, pnpm and bun install it automatically. With Yarn, add `temporal-polyfill` (`^1.0.4`) to the project's dependencies, or the commands fail because Node.js cannot find the package. That fallback is held once per process. An application that loads control-plane code in its own process, such as server code under `vite dev` with the Prisma Vite plugin or a script that calls the control client, decodes dates without its own `Temporal`, and then fails in production. An application that uses the Temporal codecs must load its own `Temporal`. A TypeScript contract file that constructs a `Temporal` value must load an implementation too.
120
120
 
121
121
  `@@index` also accepts `expression:` (instead of a fields list), `where:` (partial-index predicate), `unique:`, `type:`/`options:` (target-registered access method), and `name:` xor `map:`:
122
122