[Melbourne-pm] PostgreSQL and indexing with json types

Craig Sanders cas at taz.net.au
Tue Oct 9 15:18:14 PDT 2012

On Thu, Oct 04, 2012 at 09:56:44AM +1000, Toby Corkindale wrote:
> Hi,
> Just something interesting I noticed today..
> As you've probably already seen, PostgreSQL 9.2 added support for 
> storing JSON documents in a 'json' type field. 

this is a cool and interesting feature but it will serve to encourage
even more morons to avoid even basic/minimalist database normalisation

i'm getting tired of seeing FOSS programs that use databases just 
stuff JSON or XML or CSV or similar into a text field.

their reasoning seems to be that the data will only ever be used by
their own web app or via their REST API so there's no need to spend any
time thinking about or designing the database schema (or maybe there's
no reasoning and they're just ignorant and stupid).  Data lock-in is no
less irritating in FOSS apps than it is in proprietary apps.

also, why do something in the database server when you can do a
half-arsed emulation of it 10,000 times less efficiently in your crappy
php web app?

pg's support for JSON fields isn't a bad thing - overall, it's a good
thing...it will mitigate some of the problems - but it won't do anything
to educate web-dev morons about database design.


craig sanders <cas at taz.net.au>

BOFH excuse #233:

TCP/IP UDP alarm threshold is set too low.

More information about the Melbourne-pm mailing list