Just preference. Nothing more. Fix the issue at its source so all views 
that exist or might exist honor the demand basically. One model, many 



On Tuesday, 6 March 2018 19:13:42 UTC+11, Melvyn Sopacua wrote:
> Hi Bernd, 
> On zondag 4 maart 2018 10:41:52 CET Bernd Wechner wrote: 
> > Here is the use case: 
> > 
> >  1. Load an object from database 
> >  2. Flag it as unsaveable, not to be written back to database under any 
> >     circumstances 
> >  3. Make changes to the object (its fields) 
> >  4. Present a detail view of the object. 
> Since this is for display purposes, why does it have to remain a model? 
> -- 
> Melvyn Sopacua 

You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

Reply via email to