Split the model field options into those affecting the database and those affecting its appearance or validation.

[Lllama]

The attached documentation patch split the model field options into those affecting the model's representation in the database and those affecting its appearance or validation.

A slight confusion with 'blank' and 'null' meant that I was associating 'blank' with 'required'. This is a fair assumption for the majority of the time (admin app and forms do the same) but using the models in other scripts could cause some confusion when CharFields get created with empty strings by default.

[Lllama]

Patch to docs for splitting model options into two categories

[Chris Beaven]

as a trac readable diff (and a couple of minor changes)

[Malcolm Tredinnick]

I don't like this change. We currently have one alphabetised list of field options that the reader needs to scan. This would change that into two lists, which isn't an improvement. How about just adding a short sentence to each of the options that apply at the database level noting that fact?

[James Bennett]

Since the original point of this ticket has been vetoed, and since apparently nobody's interested enough to pick up Malcolm's suggestion, I'm going to close this.