Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
Today, we are issuing the 5.12.1
patch release to fix two small problems with our new Cloudflare D1 support.
migrate diff
and db pull
The flags --from-local-d1
and --to-local-d1
for migrate diff
and --local-d1
to db pull
we added in 5.12.0 were not working as expected when running on Windows only. This is now fixed.
šĀ Documentation: Deploying a Cloudflare worker with D1 and Prisma ORM
migrate diff
: -o
or --output
We added a new parameter --output
to migrate diff
that can be used to provide a filename into which the output of the command will be written. This is particularly useful for Windows users, using PowerShell, as using >
to write into a file creates a UTF-16 LE file that can not be read by wrangler d1 migrations apply
. Using this new option, this problem can be avoided:
npx prisma migrate diff --script --from-empty --to-schema-datamodel ./prisma/schema.prisma --output ./schema.sql
Related issues:
Today, we are excited to share theĀ 5.12.0
Ā stable releaseĀ š
šĀ Help us spread the word about Prisma by starring the repoĀ orĀ posting on XĀ about the release.
This release brings Preview support for Cloudflare D1 with Prisma ORM š„³
D1 is Cloudflareās SQLite database that can be used when deploying applications with Cloudflare.
When using Prisma ORM with D1, you can continue to: model your database with Prisma schema language, specify sqlite
as your database provider in your Prisma schema, and interact with your database using Prisma Client.
To use Prisma ORM and D1 on Cloudflare Workers or Cloudflare Pages, you need to set sqlite
as your database provider and use the @prisma/adapter-d1
Ā database adapter via theĀ driverAdapters
Ā Preview feature, released back in version 5.4.0.
Here is an example of sending a query to your D1 database using Prisma Client in your Worker:
// src/index.ts file
import { PrismaClient } from '@prisma/client'
import { PrismaD1 } from '@prisma/adapter-d1'
// Add the D1Database to the Env interface
export interface Env {
// This must match the binding name defined in your wrangler.toml configuration
DB: D1Database
}
export default {
async fetch(
request: Request,
env: Env,
ctx: ExecutionContext
): Promise<Response> {
// Make sure the database name matches the binding name in wrangler.toml and Env interface
const adapter = new PrismaD1(env.DB)
// Instantiate PrismaClient using the PrismaD1 driver adapter
const prisma = new PrismaClient({ adapter })
const users = await prisma.user.findMany()
const result = JSON.stringify(users)
return new Response(result)
},
}
šĀ Documentation: D1 Documentation
āļøĀ Blog post: Build Applications at the Edge with Prisma ORM & Cloudflare D1 (Preview)
š£Ā Share your feedback: D1 Driver Adapter
šĀ Example project: Deploy a Cloudflare Worker with D1
createMany()
for SQLiteBringing support for createMany()
in SQLite has been a long-awaited feature ā
createMany()
is a method on Prisma Client, released back in version 2.16.0, that lets you insert multiple records into your database at once. This can be really useful when seeding your database or inserting bulk data.
Here is an example of using createMany()
to create new users:
const users = await prisma.user.createMany({
data: [
{ name: 'Sonali', email: '[email protected]' },
{ name: 'Alex', email: '[email protected]' },
{ name: 'Yewande', email: '[email protected]' },
{ name: 'Angelina', email: '[email protected]' },
],
})
Before this release, if you wanted to perform bulk inserts with SQLite, you would have most likely used $queryRawUnsafe
to execute raw SQL queries. But now you donāt have to go through all that trouble š
With SQLite, createMany()
works exactly the same way from an API standpoint as it does with other databases except it does not support the skipDuplicates
option. At the behavior level, SQLite will split createMany()
entries into multiple INSERT
queries when the model in your schema contains fields with attributes like @default(dbgenerated())
or @default(autoincrement())
and when the fields are not consistently provided with values across the entries.
šDocumentation: createMany()
- Prisma Client API Reference
Decimal
data type and combining queries (batching)
findUnique()
error out when the field is of Boolean
type
relationJoins
MySQL converts nested Decimal to float
findUnique()
node-postgres
(pg) errors with misleading P2010 PrismaClientKnownRequestError
when using @prisma/adapter-pg
with SSL (?sslmode=require
)
Huge thanks to @yubrot, @skyzh, @anuraaga, @onichandame, @LucianBuzzo, @RobertCraigie, @arthurfiorette, @elithrar for helping!
Today, we are excited to share theĀ 5.11.0
Ā stable releaseĀ š
šĀ Help us spread the word about Prisma by starring the repoĀ āļøĀ orĀ posting on XĀ about the release.
Weāre thrilled to announce that support for edge function deployments with Prisma ORM is now in Preview š„³ As of this release, you can deploy your apps that are using Prisma ORM to:
In order to deploy to an edge function, youāll need to use a compatible database driver (along with its Prisma driver adapter):
pg
driver (for traditional PostgreSQL databases)@libsql/client
driver (for SQLite databases hosted via Turso)Check out our documentation to learn how you can deploy an edge function using any combination of supported edge function provider and database.
You can also read more about it in the announcement blog post!
create
operationsWith Prisma ORM, you can create multiple new records in nested queries, for example:
const user = await prisma.user.update({
where: { id: 9 },
data: {
name: 'Elliott',
posts: {
create: {
data: [{ title: 'My first post' }, { title: 'My second post' }],
},
},
},
})
In previous versions, Prisma ORM would translate this into multiple SQL INSERT
queries, each requiring its own roundtrip to the database. As of this release, these nested create
queries are optimized and the INSERT
queries are sent to the database in bulk in a single roundtrip. These optimizations apply to one-to-many as well as many-to-many relations.
With this change, using the nested create
option to create multiple records effectively becomes equivalent to using a nested createMany
operation (except that createMany
only works with one-to-many relations, whereas create
works both with one-to-many and many-to-many).
Note: Only the deepest nested operation is optimized. If a user specified
create (1) -> create (2) -> create (3)
in their query, onlycreate (3)
will be optimized.
console.log(new PrismaClient())
enum
throws error (collation cp1250_czech_cs
or similar)
NOT
condition leaks out of its desired bounds
PrismaClient
object is slow
prisma generate
on Litespeed Web Server cPanel with ssh
tsc
: Cannot find namespace 'debug'.
push
method still unimplemented for scalar lists in CockroachDB
Invalid character
error persists on 5.10.1 in Prisma Studio
runtimeDescription
is not defined error
npx prisma db pull
with DeepinOS 20.9GNU/LInux
Linux Mint
Error: Invalid character
when schema.prisma
includes Chinese/Non-ASCII characters in a comment
Today, we are excited to share theĀ 5.10.0
Ā stable releaseĀ š
šĀ Help us spread the word about Prisma by starring the repoĀ āļøĀ orĀ posting on XĀ about the release.
This release brings the optimizations for relation queries from the previous releases to MySQL as well! This means that by enabling the relationJoins
Preview feature with the mysql
database provider, you now also get access to the relationLoadStrategy
option in relation queries that let you choose whether you want to merged relations on the application- or database-level.
If you enable the relationJoins
Preview feature, you can choose between the join
and query
options:
join
(default): Sends a single query to the database and joins the data on the database-level.query
: Sends multiple queries to the database and joins the data on the application-level.To get started, enable the Preview feature in your Prisma schema:
// schema.prisma
generator client {
provider = "prisma-client-js"
previewFeatures = ["relationJoins"]
}
Be sure to re-generate Prisma Client afterwards:
npx prisma generate
And finally, specify the relation loading strategy for your relation query via the relationLoadStrategy
option as follows:
await prisma.user.findMany({
relationLoadStrategy: 'join', // or 'query'
include: {
posts: true,
},
})
Note that in the example above, the relationLoadStrategy
could be omitted altogether because join
is used as the default value.
A few notes about relationLoadStrategy
support on MySQL:
relationLoadStrategy
is supported for MySQL v8.0.14 and higher. MariaDB is not supported.LATERAL
JOINs which are used on PostgreSQL).PrismaClient
constructorThis feature enables you to configure the following transaction options on a global level via the PrismaClient
constructor:
isolationLevel
: Sets theĀ transaction isolation level. By default, this is set to the value currently configured in your database.timeout
: The maximum amount of time the interactive transaction can run before being canceled and rolled back. The default value is 5 seconds.maxWait
: The maximum amount of time Prisma Client will wait to acquire a transaction from the database. The default value is 2 seconds.Here is an example of how you can set this value globally for all transactions:
const prisma = new PrismaClient({
transactionOptions: {
isolationLevel: 'ReadCommitted',
timeout: 1_000, // 1 sec
maxWait: 2_000 // 2 sec
}
})
Thanks a lot to our fantastic community member @tockn
, who took the initiative to implement this feature in Prisma ORM š
Note that you can still override the global values by setting them on a particular transaction.
P2037
code for āToo many database connections openedā errorsWe introduced a new error code for āToo many database connections openedā errors: P2037
. You can find all error codes in our documentation.
Now available in Early Access, you can manage your workspace and configure Prisma Accelerate and Prisma Pulse directly from the terminal.
Visit our docs to learn more about the integration and try it out for yourself!
Option::unwrap()
on a None
value when using the relationJoins preview feature with driver adapters
Prisma.TransactionClient
appears to be missing types
@prisma/client
in Next.js middleware
$extends
always return any
Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.
t3.bookGenreTitle
does not exist in the current database"
relationJoins
preview feature: called Option::unwrap()
on a None
value
Today, we are issuing the 5.9.1
patch release.
In 5.9.0
we have changed our conditional exports in @prisma/client
. This resulted in broken types for TypesScript users using certain combinations of module
/moduleResolution
settings. Additionally, it also caused a regression for Next.js users which have encountered invalid error messages from our side.
You can now try out 5.9.1
and let us know if you find a bug at https://pris.ly/prisma-prisma-bug-report
Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.
#22889
Note: many issues are duplicates.
Today, we are excited to share theĀ 5.9.0
Ā stable releaseĀ šĀ
šĀ Help us spread the word about Prisma by starring the repoĀ āļøĀ orĀ posting on XĀ about the release.
This release brings a number of small improvements as we continue our work on larger features which you will hear more about in the coming weeks:
We continue our efforts of the performance of Prisma Client queries. In 5.1.0
, we introduced the RETURNING
keyword for several queries on PostrgeSQL and CockroachDB. We now expanded the use of RETURNING
to SQLite and a broader range of queries for existing databases (e.g. delete
on PostgreSQL and MongoDB). You can learn more about the optimizations of the result sets in these PRs:
When trying migrate/introspect a SQL server instance thatās unreachable, Prisma ORM now returns the correct P1001
error instead of failing without an error. Learn more in this PR: SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url.
select
queries on create/update/delete
ERROR: column "..." being dropped, try again later
when applying migrations with CRDB 23.1
Today, the only way how to use Prisma ORM in edge functions (e.g. Cloudflare Workers or Vercel Edge Functions) is by using Prisma Accelerate. However, we are actively working on making Prisma ORM compatible with edge functions natively as well. If you want to become an early tester, you can apply for the private Early Accessing program by taking this survey.
Last year, AWS announcedĀ the decision to begin charging for IPv4 addresses beginning in February 2024. This move had a major impact on Prisma Accelerate, prompting us to go all-in on IPv6. Learn more in this technical deep dive into how we approached our IPv6 migration, lessons learned, and the outcome for users of Prisma Accelerate.
Huge thanks to @laplab, @Druue, @anuraaga, @onichandame, @LucianBuzzo, @RobertCraigie, @almeidx, @victorgdb, @tinola, @sampolahtinen, @AikoRamalho, @petradonka for helping!
š Help us spread the word about Prisma by starring the repo or posting on X about the release. š
Happy New Year from your friends at Prisma! š
In the last 4 weeks, we resolved some bugs on the ORM and made some progress on some exciting features that weāre not yet ready to announce. Stay tuned for the upcoming releases, in which weāll be announcing new features. š
relationJoins
improvements: Relation loading strategy per query (Preview)In version 5.7.0, we released relationJoins
into Preview. The relationJoins
feature enables support for JOIN
s for relation queries.
This release adds support for the ability to specify the strategy used to fetch relational data per query when the Preview feature is enabled. This will enable you to choose the most efficient strategy for fetching relation data depending on your use case.
You can now load relation data using either of the following strategies:
join
ā uses JOIN
s to fetch relation dataquery
ā uses separate queries to fetch relation dataWhen the relationJoins
Preview feature is enabled, by default, the relation fetching strategy used is join
. You can override the default behavior by using the relationLoadStrategy
query option.
To get started, enable the Preview feature:
// schema.prisma
generator client {
provider = "prisma-client-js"
previewFeatures = ["relationJoins"]
}
ā¦ and specify the relation loading strategy for your query as follows:
await prisma.user.findMany({
relationLoadStrategy: 'query',
include: {
posts: true,
},
})
Try it out and share your feedback and create a bug report if you encounter any issues.
Weāre working on bringing Edge function support to Prisma ORM and we would appreciate your input by submitting a response to our survey. By filling out the survey, you will be considered for our Early Access cohort as soon as we have something for you to try out.
target
and timestamp
are undefined in info
events in Data Proxy client
timestamp
and duration
in query events with Data Proxy
citext
fields with neon database driver causes conversion error
Error validating field 'id' in model 'Post': MongoDB '@default(auto())' fields must have 'ObjectId' native type.
Huge thanks to @anuraaga, @onichandame, @LucianBuzzo, @RobertCraigie, @fqazi, @KhooHaoYit, @alencardc, @Oreilles, @tinola, @AikoRamalho, @luxaritas for helping!
Prisma Accelerate, our global database cache has served over 1 billion queries since its General Availability launch.
Weād like to give a shoutout to our team and everyone whoās been with us on this journey. Stay tuned for some exciting products and features in the pipeline for 2024!
Are you building a cool tool, extension, generator, CLI tool or anything else, for Prisma ORM? Let us know.
We would like to learn about it and feature it on our Ecosystem page.
If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you. Check out our Careers page for open positions.