![]() Transaction B: The application commits transaction B.Transaction B: createMany operation creates a new set of rows.For example, consider the following sequence of events where Transaction A and Transaction B both attempt to execute a deleteMany and a createMany operation: When two or more transactions run concurrently in certain isolation levels, timing issues can cause write conflicts or deadlocks, such as the violation of unique constraints. ![]() The timing issues discussed in this section do not apply to CockroachDB and SQLite, because these databases only support the highest Serializable isolation level.The solution in this section does not apply to MongoDB, because MongoDB does not support isolation levels.Transaction isolation levels in Microsoft SQL ServerĬockroachDB and SQLite only support the Serializable isolation level.Transaction isolation levels in PostgreSQL. ![]() To set the transaction isolation level, use the isolationLevel option in the second parameter of the API.ĭatabase-specific information on isolation levels The isolation level is not explicitly set by Prisma, so the isolation level configured in your database is used. In versions before 4.2.0 (for interactive transactions), or 4.4.0 (for sequential operations), you cannot configure the transaction isolation level at a Prisma level.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |