Cache Model interactions

Yes. It may be better to cache the view fragments.

But it might be nice to be able to manage the model results. I know we can do this the way it already is, but a conditional would have to be done for each get of the cache/db data.

I imagine the Model getting from the cache but simulating the same output it would have from the database. In order to be able to handle this data with other models.

In the inserts we could already allocate the data instantly in the cache if the data were inserted successfully in db. And analyze whether the ttl has expired or the results are not cached to return them in the selects. Also works in db updates, deletes acting in the cache. A model property could to enable and disable it and manage externally by some method.

I was modeling a database with a lot of foreign keys and I thought it would be hard to keep checking it all the time.

 natanfelles.github.io