enterprise-1.4.2

Author: rmosolgo

guides/object_cache/runtime_considerations.md

@@ -57,3 +57,9 @@ pp result.context[:object_cache]
   uncacheable: true,          # if ObjectCache found a reason that this query couldn't be cached (see `messages: ...` for reason)
 }
 ```
+
+## Manually refreshing the cache
+
+If you need to manually clear the cache for a query, pass `context: { refresh_object_cache: true, ... }`. This will cause the `ObjectCache` to remove the already-cached result (if there was one), reassess the query for cache validity, and return a freshly-executed result.
+
+Usually, this shouldn't be necessary; making sure objects update their {% internal_link "cache fingerprints", "/object_cache/schema_setup.html#object-fingerprint" %} will cause entries to expire when they should be re-executed. See also {% internal_link "Schema fingerprint", "/object_cache/schema_setup.html#schema-fingerprint %} for expiring _all_ results in the cache.

guides/object_cache/schema_setup.md

@@ -84,3 +84,17 @@ The returned strings are used as cache keys in the database -- whenever they cha
 - `def self.resolve_type(abstract_type, object, context)` which returns a GraphQL object type definition to use for `object`
 
 After your schema is setup, you can {% internal_link "configure caching on your types and fields", "/object_cache/caching", %}.
+
+## Schema Fingerprint
+
+ `ObjectCache` will also call `.fingerprint` on your Schema class. You can implement this method to return a new string if you make breaking changes to your schema, for example:
+
+ ```ruby
+class MySchema < GraphQL::Schema
+  def self.fingerprint
+    "v2" # increment this if there are breaking changes to the schema
+  end
+end
+```
+
+By returning a new `MySchema.fingerprint`, _all_ previously-cached results will be expired.

guides/pro/checksums/graphql-enterprise-1.4.2.txt

@@ -0,0 +1 @@
+cce6aca47058577462d4bf51c02b578c6aaf7bb47335e3435129efc9662e37e13756542d40ce728702a373d4e93416bb72202dfa9781bcc3de61c81b29471a5a