One thing I&#x27;m wondering about graphql is how does it know when something changed in the db and should be re-queried. For example, I fetch some movies in my front-end webapp and they are cached. Then, later on, I query that movie again but something changed on the server, say the producer had a typo in their name. In that situation, it seems like graphql will only fetch the new fields I&#x27;m querying, and not what&#x27;s already cached.<p>I understand it&#x27;s a caching problem which is hard (I know that joke), but I&#x27;m wondering specifically how it&#x27;s handled with a graph query.<p>The way I&#x27;ve been doing it is using a SQL structured on the front-end and downloading the main table&#x2F;rows + changes. But graphql seems to be downloading and aggressively caching without keeping track of timestamp.