Malcolm Tredinnick 70e59aeaf8 Be very clear about when it's appropriate to use defer() and only(). ... I've been seeing a bit of over-reliance on defer() and only() in code around the place and it's generally better modelled with normalised data or shadow (unmanaged) models. This commit makes this position clearer. git-svn-id: http://code.djangoproject.com/svn/django/trunk@16692 bcc190cf-cafb-0310-a4f2-bffc1f526a37		2011-08-26 06:19:30 +00:00
..
fields.txt	Fixed #16498 -- Fixed typo in GenericIPAddressField docs. Thanks, JshWright.	2011-07-29 09:39:49 +00:00
index.txt	Fixed #14141: docs now use the :doc: construct for links between documents.	2010-08-19 19:27:44 +00:00
instances.txt	Fixed #16090, #16091, #16114 - Typos in docs; thanks teraom.	2011-05-31 09:42:19 +00:00
options.txt	Be very clear about when it's appropriate to use defer() and only().	2011-08-26 06:19:30 +00:00
querysets.txt	Be very clear about when it's appropriate to use defer() and only().	2011-08-26 06:19:30 +00:00
relations.txt	Fixed #14840 -- Added crossrefs to related objects reference docs. Thanks to adamv for the report and patch.	2010-12-06 11:49:31 +00:00