On Mar 1, 2014, at 9:14 AM, Martin Matusiak <[email protected]> wrote:
> Is there a rationale for why we don't do this? Perhaps because handling data constraint is the db job? In the case of sqlite, which is very free form, simply define the proper check constraints. For example: create table foo ( bar text not null, check( typeof( bar ) = 'text' and length( bar ) <= 10 ) ); sqlite> insert into foo values( 1 ); Error: CHECK constraint failed: foo sqlite> insert into foo values( '12345678901' ); Error: CHECK constraint failed: foo -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/69E6D147-96ED-45FB-95CD-40D238C8CB20%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
