Add a bit more detail to latest TIL

README.md

@@ -10,7 +10,7 @@ pairing with smart people at Hashrocket.
 
 For a steady stream of TILs, [sign up for my newsletter](https://crafty-builder-6996.ck.page/e169c61186).
 
-_1347 TILs and counting..._
+_1348 TILs and counting..._
 
 ---
 
@@ -760,6 +760,7 @@ _1347 TILs and counting..._
 
 - [Apply Separate Formatting With A Blank Line](prisma/apply-separate-formatting-with-a-blank-line.md)
 - [Batch Insert Records With createMany](prisma/batch-insert-records-with-create-many.md)
+- [Configure Client To Log SQL Queries](prisma/configure-client-to-log-sql-queries.md)
 - [Execute A Raw SQL Query](prisma/execute-a-raw-sql-query.md)
 - [Grab A Limited Set Of Records](prisma/grab-a-limited-set-of-records.md)
 - [Open Connections To Multiple Databases](prisma/open-connections-to-multiple-databases.md)

prisma/configure-client-to-log-sql-queries.md

@@ -0,0 +1,33 @@
+# Configure Client To Log SQL Queries
+
+During development, especially while debugging, it can be helpful to see the
+actual SQL queries generated by Prisma queries we are formulating. Because an
+ORM is an abstraction over SQL, it isn't always obvious what the resulting SQL
+will turn out to be.
+
+By adding the `log` configuration to where we initialize our Prisma client, we
+can tell it to log things like errors and the SQL of the queries it executes.
+
+```javascript
+export const prisma =
+  new PrismaClient({
+    log: ['error', 'query']
+  })
+```
+
+If we only want the SQL logged in development, we could do something like this:
+
+```javascript
+export const prisma =
+  new PrismaClient({
+    log:
+      process.env.NODE_ENV === 'development'
+        ? ['query', 'error']
+        : ['error'],
+  })
+```
+
+If we look in our app server logs when a code path that contains a Prisma query
+executes, we'll see a line for each SQL statement.
+
+[source](https://github.com/prisma/prisma/discussions/3967)