Tuesday 15 June 2010

Is there any negatives to storing JSON in MySQL? -



Is there any negatives to storing JSON in MySQL? -

i building complex ordering scheme , struggling whether should store of more detailed info in single column json or if should create multiple tables , logic maintain json out of picture.

since each order have multiple required dates, ship dates, parts, kits (collections of parts), , more. seems easier store json of single 'order'row.

are there major downwards sides doing this?

json geared more towards short term storage send info 1 thing another. horribly inefficient space , computationally wise long term storage compared database. loose ability query info straight without parsing first (e.g "select * table orderdate < today"). you'll have develop own tools view data, since if seek view in database directly, run together.

in short, bad idea.

mysql json database laravel-4

No comments:

Post a Comment