Update content/200-orm/200-prisma-client/100-queries/090-raw-database…

…-access/050-raw-queries.mdx
prisma · Mar 21, 2024 · 8f95c4c · 8f95c4c
1 parent 64e4ad6
commit 8f95c4c
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/...0-orm/200-prisma-client/100-queries/090-raw-database-access/050-raw-queries.mdx b/...0-orm/200-prisma-client/100-queries/090-raw-database-access/050-raw-queries.mdx
@@ -153,7 +153,7 @@ result.forEach((x) => {
 })
 ```
 
-For regular CRUD querues, the Prisma Client query engine standardizes the return type for all databases. **Using the raw queries does not**. If the database provider is MySQL, the returned values are `1` or `0`. However, if the database provider is PostgreSQL, the values are `true` or `false`.
+For regular CRUD queries, the Prisma Client query engine standardizes the return type for all databases. **Using the raw queries does not**. If the database provider is MySQL, the returned values are `1` or `0`. However, if the database provider is PostgreSQL, the values are `true` or `false`.
 
 > **Note**: Prisma sends JavaScript integers to PostgreSQL as `INT8`. This might conflict with your user-defined functions that accept only `INT4` as input. If you use `$queryRaw` in conjunction with a PostgreSQL database, update the input types to `INT8`, or cast your query parameters to `INT4`.