Prisma ORM 6.18.0, Postgres Database Metrics and Config Modernization

In-depth Database Metrics

Last release, we included a new workspace metrics overview, so folks can get a quick glance on their usage data across your entire workspace. Now, we’ve added more insights into your database usage with database metrics.

Here, you can view the usage of an individual database, with stats on:

• Number of operations
• Cache utilization
• Average Response Size
• Total egress
• Average query duration

In addition to these stats, you can also get insight into ways to improve caching and overall database performance

Init with prisma.config.ts automatically

As we prepare for Prisma v7, we’re moving more functionality into the prisma.config.ts file so developers can adopt it and not be caught off guard. To assist with this, we’ve moved to make prisma init automatically create a config file when you start a new project. Now, fields that have historically been in the schema.prisma file can be set in your config file. This will become the new place for these fields come Prisma v7.

Define your datasource in prisma.config.ts

If you’re adopting the new prisma.config.ts setup in your projects, version 6.18.0 brings the ability to set your datasource directly in your config file. Once this is in your config file, any datasource set in your schema.prisma will be ignored. To set the datasource, we also must include the new engine key which we can set to "classic", which will be required for Prisma v7

Migrating to prisma.config.ts

A good amount of work we’ve done in 6.18.0 has been to get the Prisma Config to match functionality to the Schema file. For with this release, we’d like to encourage developer to begin migrating to the Prisma Config. This way we can gather more feedback before we hit our next major release and can address any gaps in functionality. As part of this, we’ve included a small migration guide below for developers to follow.

1. Updates to schema.prisma

2. Add any drivers you may need for your database

If you’re using, for example PostgresSql, you’ll need to add the necessary driver. In this case @prisma/adapter-pg can be used. If you’re using Prisma Postgres, then there’s no extra steps needed here.

Then in your PrismaClient setup, add the adapter as an optional parameter.

3. Migrate to prisma.config.ts

The prisma.config.ts is the new home for configuring your Prisma project.

For a full reference of the options that can be used in Prisma Config, see the docs.

Be sure to follow us on social media to stay up to date with all the latest release of Prisma ORM and Prisma Postgres

• X/Twitter
• Bluesky
• LinkedIn
• Discord