Does Hydrate support caching?
Yes, and no. One man’s cache is another man’s crock, so we have to be careful to define what we mean here. Hydrate currently prefers to promote a paradigm in which objects are read from the database each time a request is made, thus in effect, handing the responsibility for caching down to the database engine (many of which do a pretty good job). Hydrate works with the database drivers to permit them to cache queries and result sets. Once the objects have been read into memory, you are also free to decide which of them you keep in memory between requests, and which you discard from memory.
