You can only have one datasource block in a schema.Available in preview for PostgreSQL only in Prisma versions 4.5.0 and later. List of strings (PostgreSQL extension names)Īllows you to represent PostgreSQL extensions in your schema. The field is named relationMode in versions 4.5.0 and later, and was previously named referentialIntegrity. Sets whether referential integrity is enforced by foreign keys in the database or emulated in the Prisma Client. If you are using a prisma:// URL in the url argument, you may use the Data Browser as an alternative to Prisma Studio. The only exception to this is the prisma studio command. If you use a connection pooler URL in the url argument (for example, if you use the Data Proxy or pgBouncer), Prisma CLI commands that require a direct connection to the database use the URL in the directUrl argument. Allows you to use a cloud-hosted database as the shadow database.Ĭonnection URL for direct connection to the database. Most connectors use the syntax provided by the database.Ĭonnection URL to the shadow database used by Prisma Migrate. More than one of these libraries might be available on a particular machine, so configure does not automatically choose one.String ( postgresql, mysql, sqlite, sqlserver, mongodb, cockroachdb)ĭescribes which data source connectors to use.Ĭonnection URL including authentication info. When invoking configure, specify -with-uuid=bsd to use the BSD functions, or -with-uuid=e2fs to use e2fsprogs' libuuid, or -with-uuid=ossp to use the OSSP UUID library. On Linux, macOS, and some other platforms, suitable functions are provided in the libuuid library, which originally came from the e2fsprogs project (though on modern Linux it is considered part of util-linux-ng). On FreeBSD and some other BSD-derived platforms, suitable UUID creation functions are included in the core libc library. uuid-ossp can now be built without the OSSP library on some platforms. While the OSSP UUID library can still be found at, it is not well maintained, and is becoming increasingly difficult to port to newer platforms. Historically this module depended on the OSSP UUID library, which accounts for the module's name. Version 5 should be preferred over version 3 because SHA-1 is thought to be more secure than MD5. This function generates a version 5 UUID, which works like a version 3 UUID except that SHA-1 is used as a hashing method. Uuid_generate_v5(namespace uuid, name text) This function generates a version 4 UUID, which is derived entirely from random numbers. The generation of UUIDs by this method has no random or environment-dependent element and is therefore reproducible. The name parameter will be MD5-hashed, so the cleartext cannot be derived from the generated UUID. SELECT uuid_generate_v3(uuid_ns_url(), '') (It could be any UUID in theory.) The name is an identifier in the selected namespace. The namespace should be one of the special constants produced by the uuid_ns_*() functions shown in Table F.33. This function generates a version 3 UUID in the given namespace using the specified input name. Uuid_generate_v3(namespace uuid, name text) This function generates a version 1 UUID but uses a random multicast MAC address instead of the real MAC address of the computer. Note that UUIDs of this kind reveal the identity of the computer that created the identifier and the time at which it did so, which might make it unsuitable for certain security-sensitive applications. This involves the MAC address of the computer and a time stamp. This function generates a version 1 UUID.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |