# Native database functions

In PostgreSQL, some [native database functions](/guides/prisma-schema-v6-data-model-unsupported-database-features#native-database-functions) are part of optional extensions. For example, in PostgreSQL versions 12.13 and earlier the `gen_random_uuid()` function is part of the [`pgcrypto`](https://www.postgresql.org/docs/10/pgcrypto.html) extension.

To use a PostgreSQL extension, you must install it on the file system of your database server and then activate the extension. If you use Prisma Migrate, this must be done as part of a migration.

:::callout{intent="warning"}
Do not activate extensions outside a migration file if you use Prisma Migrate. The [shadow database](/guides/prisma-migrate-v6-understanding-prisma-migrate-shadow-database) requires the same extensions. Prisma Migrate creates and deletes the shadow database automatically, so the only way to activate an extension is to include it in a migration file.
:::

In Prisma ORM versions 4.5.0 and later, you can activate the extension by declaring it in your Prisma schema with the [`postgresqlExtensions` preview feature](/guides/prisma-schema-v6-postgresql-extensions):

```title="schema.prisma"
generator client {

  provider        = "prisma-client"

  output          = "./generated"

  previewFeatures = ["postgresqlExtensions"] 

}

datasource db {

  provider   = "postgresql"

  extensions = [pgcrypto] 

}
```

You can then apply these changes to your database with Prisma Migrate. See [How to migrate PostgreSQL extensions](/guides/prisma-schema-v6-postgresql-extensions) for details.

In earlier versions of Prisma ORM, you must instead add a SQL command to your migration file to activate the extension. See [How to install a PostgreSQL extension as part of a migration](#how-to-install-a-postgresql-extension-as-part-of-a-migration).

## [How to install a PostgreSQL extension as part of a migration](#how-to-install-a-postgresql-extension-as-part-of-a-migration)

This section describes how to add a SQL command to a migration file to activate a PostgreSQL extension. If you manage PostgreSQL extensions in your Prisma Schema with the `postgresqlExtensions` preview feature instead, see [How to migrate PostgreSQL extensions](/guides/prisma-schema-v6-postgresql-extensions).

The following example demonstrates how to install the `pgcrypto` extension as part of a migration:

1. Add the field with the native database function to your schema:

   ```
   model User {

     id String @id @default(dbgenerated("gen_random_uuid()")) @db.Uuid

   }
   ```

   If you include a cast operator (such as `::TEXT`), you must surround the entire function with parentheses:

   ```
   @default(dbgenerated("(gen_random_uuid()::TEXT)"))
   ```

2. Use the `--create-only` flag to generate a new migration without applying it:

   ::::tabs
   :::tab{title="bun"}
   ```
   bunx prisma migrate dev --create-only
   ```
   :::

   :::tab{title="pnpm"}
   ```bash
   pnpm prisma migrate dev --create-only
   ```
   :::

   :::tab{title="yarn"}
   ```bash
   yarn prisma migrate dev --create-only
   ```
   :::

   :::tab{title="npm"}
   ```bash
   npx prisma migrate dev --create-only
   ```

   3. Open the generated `migration.sql` file and enable the `pgcrypto` module:

      ```sql
      CREATE EXTENSION IF NOT EXISTS pgcrypto;

      ADD COLUMN "id" UUID NOT NULL DEFAULT gen_random_uuid(),
      ADD PRIMARY KEY ("id");
      ```

   4. Apply the migration:
   :::
   ::::

3. Open the generated `migration.sql` file and enable the `pgcrypto` module:

   ```
   CREATE EXTENSION IF NOT EXISTS pgcrypto;

   ADD COLUMN "id" UUID NOT NULL DEFAULT gen_random_uuid(),

   ADD PRIMARY KEY ("id");
   ```

4. Apply the migration:

   ::::tabs
   :::tab{title="bun"}
   ```
   bunx prisma migrate dev
   ```
   :::

   :::tab{title="pnpm"}
   ```bash
   pnpm prisma migrate dev
   ```
   :::

   :::tab{title="yarn"}
   ```bash
   yarn prisma migrate dev
   ```
   :::

   :::tab{title="npm"}
   ```bash
   npx prisma migrate dev
   ```

   Each time you reset the database or add a new member to your team, all required functions are part of the migration history.
   :::
   ::::

Each time you reset the database or add a new member to your team, all required functions are part of the migration history.

## Related pages

- [Authentication & Tools](./authentication-tools-index.md)
- [Build](./build-index.md)
- [Changelog](../changelog.md)
- [Concepts](./concepts-index.md)
- [Console commands](./console-commands-index.md)
- [Contract Authoring](./contract-authoring-index.md)
- [Core Concepts](./core-concepts-index.md)
- [Data Modeling](./data-modeling-index.md)
- [Database](./database-index.md)
- [DB commands](./db-commands-index.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.