Django

Code

Ticket #7634 (closed: wontfix)

Opened 2 years ago

Last modified 4 months ago

Using auto_now or auto_now_add should raise a DeprecationWarning

Reported by: Alex Assigned to: nobody
Milestone: Component: Database layer (models, ORM)
Version: SVN Keywords:
Cc: jezdez Triage Stage: Accepted
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

To my understanding these are both slated for eventual removal in favor of the default kwarg and overiding the save() method, therefore they should raise a DeprecationWarning? to alert people of this fact.

Attachments

auto_add.diff (0.7 kB) - added by Alex on 07/06/08 23:13:51.
Raises a deprecation warning

Change History

07/06/08 23:13:51 changed by Alex

  • attachment auto_add.diff added.

Raises a deprecation warning

07/07/08 12:57:24 changed by programmerq

  • needs_better_patch changed.
  • has_patch set to 1.
  • stage changed from Unreviewed to Accepted.
  • needs_tests changed.
  • needs_docs changed.

07/13/08 05:36:47 changed by anonymous

Remember to close #7634.

01/02/09 16:59:06 changed by jezdez

  • cc set to jedzez.

01/03/09 20:03:39 changed by mtredinnick

  • status changed from new to closed.
  • resolution set to wontfix.

For better or worse, these features are in 1.0 and so aren't going away in the near future.

11/06/09 17:20:10 changed by jezdez

  • cc changed from jedzez to jezdez.

Add/Change #7634 (Using auto_now or auto_now_add should raise a DeprecationWarning)




Change Properties
Action