Reorganize the Schema Cache information into a separate reference page (#404)

api.rst

@@ -990,6 +990,8 @@ In this case, only **source**, **publication_date** and **figure** will be inser
 Using this also has the side-effect of being more efficient for :ref:`bulk_insert` since PostgREST will not process the JSON and
 it'll send it directly to PostgreSQL.
 
+.. _upsert:
+
 UPSERT
 ------
 
@@ -1109,18 +1111,6 @@ For instance, assume we have created this function in the database.
 
   Whenever you create or change a function you must refresh PostgREST's schema cache. See the section :ref:`schema_reloading`.
 
-  If the schema cache is not refreshed, PostgREST will assume :code:`text` as the default type for function arguments. This could
-  lead to getting error responses like:
-
-  .. code-block:: json
-
-     {
-      "hint":"No function matches the given name and argument types. You might need to add explicit type casts.",
-      "details":null,
-      "code":"42883",
-      "message":"function test.add_them(a => text, b => text) does not exist"
-     }
-
 The client can call it by posting an object like
 
 .. code-block:: http