Melvyn, 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 views.
Regards, Bernd. 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to firstname.lastname@example.org. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a5fc94e3-a2ae-4433-9880-9309843d6145%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.