#21459: Allow easy reload of appcache.
-------------------------------------+-------------------------------------
     Reporter:  zaharid@…            |                    Owner:  nobody
         Type:  New feature          |                   Status:  closed
    Component:  Core (Cache system)  |                  Version:  1.6
     Severity:  Normal               |               Resolution:  wontfix
     Keywords:  interactive, models  |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by danpetrikin):

 Replying to [comment:1 apollo13]:
 > See #3591 for more issues into that direction; supporting `reload()`
 might be a nice side-effect, but imo not worth any effort.

 I'd like to know details as to why this isn't worth any effort.

 Models in modern software are getting defined more frequently at runtime.
 It's been quite a pain researching how I tell Django that "my model
 definition has changed, please reload the model definition"

 Simple python reloads have not sufficed nor has working with the available
 information on appcache. Unless I'm just incredibly stupid, which I never
 rule out as a possibility, I don't see any information within the
 documentation on AppCache or how it gets loaded.

 Granted, I am using a fork of Django that supports nosql, and am defining
 models on the fly based on values of other models. However, I can easily
 see a similar use case for anyone who wants to automate migrations and run
 them based on other model changes, still supporting dynamic models
 (although it'd probably crush performance on a traditional SQL DB).

 Without ease of access to model reloads within the Django framework, truly
 sophisticated systems that are programmed to respond to their own internal
 data states with additional logic must come up with their own solutions.
 I'm sorry if I seem like an edge case, but I have a feeling in the coming
 years runtime generated, and altered, model definitions will become a far
 more standard need within the industry.

--
Ticket URL: <https://code.djangoproject.com/ticket/21459#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.4abaa636e2d47d895496b8090403b89e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to