Changes between Version 19 and Version 20 of DjangoSpecifications/Core/SingleInstance

Timestamp:

Mar 25, 2008, 8:30:13 AM (17 years ago)

Author:

Philippe Raoult

Comment:

--

DjangoSpecifications/Core/SingleInstance

@@ -116 +116 @@
 == Discussions ==
 === Internal API ===
-The current patch design overrides the !__call!__ method for the model base which means it automatically returns singleton instances when available. This is convenient because XXX (David or Brian: feel free to fill this out).
+''(David)'' The current patch design overrides the !__call!__ method for the model base which means it automatically returns singleton instances when available. This is convenient because XXX (David or Brian: feel free to fill this out).
 
-Another approach would be to make this explicit and have a simple API along the lines of:
+''(Philippe)'' Another approach would be to make this explicit and have a simple API along the lines of:
 {{{
 class ModelBase:
@@ -129 +129 @@
 === Default behavior ===
 Should this feature be enabled by default ? 
- * Philippe: It should be because it really makes the ORM behave more correctly but for the sake of backward compatibility let's fist commit off by default. We can 
-change the default parameter value later, and in the meantime honor a global setting to turn it on for all models.
+ * ''(Philippe)'' It should be because it really makes the ORM behave more correctly but for the sake of backward compatibility let's fist commit off by default. We can change the default parameter value later, and in the meantime honor a global setting to turn it on for all models.
 
- * David: This would always be enabled. You cannot turn it off. If stuff is broken by having this on then it should be broken.
-This can cause problems with serializers, and things that modify querysets and shouldn't (e.g. .extra). That is the only reason it should be turned off. If those problems are addressed there is no reason to use #17 and to have it enabled 100% of the time.
+ * ''(David)'' This would always be enabled. You cannot turn it off. If stuff is broken by having this on then it should be broken. This can cause problems with serializers, and things that modify querysets and shouldn't (e.g. .extra). That is the only reason it should be turned off. If those problems are addressed there is no reason to use #17 and to have it enabled 100% of the time.
 
 === extra, values ===