[eluser]TheFuzzy0ne[/eluser]
Sometimes the forum does that when you've had the reply page open too long. I've learnt that hitting the back button, and clicking Fast Reply (assuming that's what you did), should show your post again. Then you need to copy it, and either refresh the page to use Fast Reply again, or just go through to the Post Reply page, and paste it in there.
I agree, caching objects only lasts for that request, but let's say I called get_root_node several times (once from my app, and several times from within the object itself), that's what the caching is for. Instead of making a call to the database several times, only one call is made, and then the cached data is passed back for subsequent requests. It sounded OK to me, but I couldn't find any examples to back it up, which is why I have been left so confused. I want to create the model part so it has the smarts to cut down on database calls, but I can't decide if that's good, or just adding unnecessary complications. After all, less calls to the database is certainly better.
It was your saying "has many", "has one", "belongs to one" and so on. As that's how you describe database objects in ORM, I assumed you used it.
