I'm using version 2.1.8 and can't seem to find any explanations. Is this as intended? For many applications it would be great to avoid hitting the database when loading newly created items.

Thanks,
Steve

Can anyone at least describe or point me at docs for where the second level cache is populated/invalidated?

Steve

What if a trigger was associated with the save - such as setting a created date field?

Thanks for the reply. I am looking into manually adding to the second level cache after a save but I'm wondering why it wasn't done in the first place. It makes me think there is some fundamental issue with doing that.