Ah, sounds like you are again thinking about bitemporal reasoning over relational data. We are not really built for that use case. Instead of focusing on fund

Ah, sounds like you are again thinking about bitemporal reasoning over relational data. We are not really built for that use case. Instead of focusing on fundamentally relational data such as people or jobs (which you are free to store alongside our stuff, using plain postgres functionality), we store event or metrics data. This data can be easily joined against the relational data (e.g., using a person_id stored in both event and relational tables).