Prisma 5 Prisma 6: los breaking changes que encontré en mi schema real y cómo los resolví sin romper producción
The article discusses the breaking changes encountered when upgrading from Prisma 5 to Prisma 6. It emphasizes the importance of understanding these changes to avoid runtime issues. The author provides a checklist and analysis of three significant changes that impact the upgrade process.
- ▪Prisma 6 introduces changes that the TypeScript compiler does not flag, which can lead to runtime errors.
- ▪The upgrade process requires attention to three specific behavioral changes in queries and transactions.
- ▪One major change is that the selectRelationCount feature is no longer opt-in, affecting how relationships are counted in queries.
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 Jun 3 • Originally published at juanchi.dev Prisma 5 Prisma 6: los breaking changes que encontré en mi schema real y cómo los resolví sin romper producción #spanish #espanol #typescript #backend Prisma 5 → Prisma 6: los breaking changes que encontré en mi schema real y cómo los resolví sin romper producción La solución correcta para migrar de Prisma 5 a Prisma 6 sin romper nada es no correr el upgrade el viernes. Sé que suena obvio.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
