Chaos update: it happened again. π
Chaos update: it happened again. π
Just posted about surviving my last round of chaos β cryptomining attacks, server migrations, payment rejections. Thought I was done.
Then came a Shopify mobile CSS adaptation project that broke everything I thought I knew about responsive design.
Survived that too.
Turns out the valley of despair has a new wing.
Now I'm stuck on a UTF-8 encoding issue in my English learning app (Next.js 15 + Prisma 5 + MySQL 8 in Docker).
Chinese characters stored in MySQL are coming back garbled through Prisma's $queryRaw β showing Γ¨βΉΒΉΓ¦ΕΎΕ instead of θΉζ. Table charset is already utf8mb4_unicode_ci. Prepending SET NAMES utf8mb4 helps inconsistently.
Looking for a way to enforce utf8mb4 globally at the connection level β a Prisma datasource option or connection string parameter, so I'm not patching it query by query.
Still here. Still building. Send help. π
#Prisma #MySQL #Nextjs #webdev #helpwanted #buildinpublic
