I understand the automated setting would be to have models you define in models.py become database tables.

I'm attempting to define models that will not be tables. They have to store dynamic data (that people get and configure from APIs), whenever a user looks for something. This data must be put together, after which once the user is completed, thrown away.

formerly I had been using database tables with this. It permitted me to complete such things as "Outings.objects.all" in almost any view, and pass that to the template, because it all originated from one databases. I have heard you can easily not "save" the model instantiation, after which it does not save towards the database, but I have to access this data (that I have put together in a single view), in multiple other sights, to control it and display it . . . basically don't save i can not can get on, basically do save, then it's inside a database (which may have concurrency difficulties with multiple customers)

I do not actually want to pass around a dictionary/list, and I am not really sure the way i was do this basically needed to.



Use database or file based sessions.

Use Django's cache framework to keep data and share it between sights.

Just seems like a normal [cde] in my experience.

Possibly use the middleware to instantiate it when request is available in and discard when request is completed. One access strategy may be to add it towards the request object itself but ymmv.