| 1 | | @loic84 - he may well be advised to use `datetime.now`, but that doesn't change the fact that using ``datetime.now()`` is a valid value for a default. It's an unusual value, to be sure, but it is a *valid* value. Off the top of my head, one possible use case would be to set up a membership model where memberships start Jan 1 2014, unless otherwise specified. |
| | 1 | @loic84 - he may well be advised to use `datetime.now`, but that doesn't change the fact that using `datetime.now()` is a valid value for a default. It's an unusual value, to be sure, but it is a *valid* value. Off the top of my head, one possible use case would be to set up a membership model where memberships start Jan 1 2014, unless otherwise specified. |