News for hackers. Stuff that matters.

A comment on Django 3.1. Parent comment

Re:Django 3.1 by OJFord on Tuesday August 04, 2020 @06:30AM (#24048532)
Access, but not constrain or type-check.

And it's just harder to use, I'm with it being generally a 'mistake' (in the 'you will regret this later' sense) - it's better than text, but I'm in the camp of as much structure as possible ('you will thank yourself later').

[ Parent | on HN ]
Re:Django 3.1 by formerly_proven on Tuesday August 04, 2020 @10:19AM (#24050222)
> Access, but not constrain or type-check.

You can create CHECK constraints involving JSON operations in postgres, which is the same way you'd enforce any constraint.

[ Parent | on HN ]
Re:Django 3.1 by theptip on Tuesday August 04, 2020 @11:15AM (#24050789)
Manually, right? Django autogenerates all of the SQL schema for you on non-JSON fields. You could replicate that work, but that sounds tedious.
[ Parent | on HN ]