<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Database Schema on No Semicolons</title><link>https://nosemicolons.com/tags/database-schema/</link><description>Recent content in Database Schema on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 12 Sep 2026 11:50:05 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/database-schema/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Model Alignment Crisis: How I Lost 40 Hours Because GPT-4 Thinks My Database Schema Is Wrong</title><link>https://nosemicolons.com/posts/ai-model-alignment-crisis-database-schema-conflicts/</link><pubDate>Sat, 12 Sep 2026 11:50:05 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-model-alignment-crisis-database-schema-conflicts/</guid><description>&lt;p>Ever had an AI confidently rewrite your entire database layer because it &amp;ldquo;knows better&amp;rdquo; than your existing architecture? Yeah, me too. And it cost me 40 hours of debugging hell that I&amp;rsquo;ll never get back.&lt;/p>
&lt;p>Last month, I was working on a feature for a legacy e-commerce system. The database schema was&amp;hellip; let&amp;rsquo;s call it &amp;ldquo;creative.&amp;rdquo; Years of evolution had led to some unconventional patterns that worked perfectly but looked weird to fresh eyes. I figured GPT-4 could help me quickly generate some new API endpoints.&lt;/p></description></item></channel></rss>