Prisma Query Logging and PostgreSQL: Where the ORM Ends and the Database Begins
The article discusses the limitations of Prisma's query logging in relation to PostgreSQL database performance. It emphasizes that while Prisma logs provide insights into query execution from the ORM's perspective, they do not reflect the actual execution time within PostgreSQL. The author warns against confusing client-side duration with database execution time, which can lead to misguided optimization efforts.
- ▪Prisma query logs show the query and its duration from the ORM's perspective, not the actual execution time in PostgreSQL.
- ▪To accurately measure execution time in PostgreSQL, tools like pg_stat_statements or EXPLAIN ANALYZE should be used.
- ▪Confusing client duration with PostgreSQL execution time can lead to incorrect assumptions about query performance.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 885942) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Juan Torchia Posted on May 25 • Originally published at juanchi.dev Prisma Query Logging and PostgreSQL: Where the ORM Ends and the Database Begins #english #typescript #backend #nextjs Prisma Query Logging and PostgreSQL: Where the ORM Ends and the Database Begins I turned on query logging in Prisma, watched queries rolling into the console, and assumed I had full visibility into what was happening in the database. Spoiler: I didn't.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
