tickets_full: 3328

This data as json

id created changetime last_pulled_from_trac stage status component type severity version resolution summary description owner reporter keywords easy has_patch needs_better_patch needs_tests needs_docs ui_ux
3328 2007-01-19 03:08:05 2007-09-16 16:06:46 2019-06-24 00:50:41.919241 Design decision needed closed Database layer (models, ORM)     master wontfix null=True should imply blank=True For models, I can't ever think of a case when you would want `null=True` and '''not''' want `blank=True`. If there is, it's definitely rare, so having to enter both for the normal case seems redundant. Currently, for model fields, `blank` always defaults to `False`. This proposal is that `blank` is set to whatever `null` is set to unless explicitly given. nobody SmileyChris   0 1 0 0 0 0
Powered by Datasette · Query took 4.17ms