Open raymondKelly opened 3 months ago
When reviewing other adapters it looked like there was a fix put in place in the adapter to handle an issue in a downstream package(node-postgres). I pulled across that fix so as to reduce the risk of an unknown bug in the aurora adapter as seen here https://github.com/limelighthealth/prisma-adapter-aurora/blob/43a77eabb800e68118c653b834c115c0ad816aea/packages/aurora-prisma-adapter/src/conversion.ts#L40 We should touch base with the Prisma team to see if they took the fix that was merged by node-postgres.
When reviewing other adapters it looked like there was a fix put in place in the adapter to handle an issue in a downstream package(node-postgres). I pulled across that fix so as to reduce the risk of an unknown bug in the aurora adapter as seen here https://github.com/limelighthealth/prisma-adapter-aurora/blob/43a77eabb800e68118c653b834c115c0ad816aea/packages/aurora-prisma-adapter/src/conversion.ts#L40 We should touch base with the Prisma team to see if they took the fix that was merged by node-postgres.