Prefer Strict Tables in SQLite

A quiet little database setting just sparked a surprisingly passionate mini-revolt. The post argues that SQLite — a tiny, wildly popular way apps store data — has an underrated feature called STRICT that stops people from shoving the wrong kind of info into the wrong box. In plain English: if a field is meant for numbers, STRICT helps block nonsense text from sneaking in. The writer’s pitch is simple: this should save developers from embarrassing mistakes, weird typos, and those cursed moments when a table says one thing but stores another.

But the real juice is in the comments, where the crowd immediately turned this into a “why on earth is this not already normal?” debate. One commenter flatly said it “really should be default,” while another confessed they genuinely assumed it already was. That mood — half shock, half exhausted resignation — became the vibe of the thread. There wasn’t full-on bloodsport, but there was a spicy little tension: people clearly love SQLite and its creator, yet still want this stricter behavior turned on by default. One fan practically delivered a standing ovation and a complaint in the same breath.

There was also a tiny side quest around the oddly named ANY option, which allows flexibility even in a strict table. Most people shrugged, but one commenter swooped in with a practical use: audit logs. So yes, amid the “make it default!” chants, the community still found time for a niche power-user flex. Classic internet.