add breaking changes
This commit is contained in:
committed by
Steve Chavez
parent
dec1e03a0e
commit
c56108b8a9
@@ -415,42 +415,3 @@ You can call overloaded functions with different number of arguments.
|
||||
.. important::
|
||||
|
||||
Overloaded functions with the same argument names but different types are not supported.
|
||||
|
||||
.. _bulk_call:
|
||||
|
||||
Bulk Call
|
||||
---------
|
||||
|
||||
It's possible to call a function in a bulk way, analogously to :ref:`bulk_insert`. To do this, you need to add the
|
||||
``Prefer: params=multiple-objects`` header to your request.
|
||||
|
||||
.. tabs::
|
||||
|
||||
.. code-tab:: http
|
||||
|
||||
POST /rpc/add_them HTTP/1.1
|
||||
Content-Type: text/csv
|
||||
Prefer: params=multiple-objects
|
||||
|
||||
a,b
|
||||
1,2
|
||||
3,4
|
||||
|
||||
.. code-tab:: bash Curl
|
||||
|
||||
curl "http://localhost:3000/rpc/add_them" \
|
||||
-X POST -H "Content-Type: text/csv" \
|
||||
-H "Prefer: params=multiple-objects" \
|
||||
--data-binary @- << EOF
|
||||
a,b
|
||||
1,2
|
||||
3,4
|
||||
EOF
|
||||
|
||||
.. code-block:: json
|
||||
|
||||
[ 3, 7 ]
|
||||
|
||||
If you have large payloads to process, it's preferable you instead use a function with an :ref:`array parameter <s_procs_array>` or JSON parameter, as this will be more efficient.
|
||||
|
||||
It's also possible to :ref:`Specify Columns <specify_columns>` on functions calls.
|
||||
|
||||
@@ -13,11 +13,16 @@ Documentation improvements
|
||||
- Split :ref:`authn` into :ref:`db_authz` and :ref:`sql_user_management`.
|
||||
- Split :ref:`admin` into :ref:`intgrs` and :ref:`nginx`.
|
||||
|
||||
Bug fixes
|
||||
---------
|
||||
|
||||
Breaking changes
|
||||
----------------
|
||||
|
||||
Bug fixes
|
||||
---------
|
||||
- Removed Bulk Call with ``Prefer: params=multiple-objects`` on Stored Procedures.
|
||||
- To comply with `RFC 9110 <https://www.rfc-editor.org/rfc/rfc9110.html#name-range>`_, the Range header is now only considered on GET.
|
||||
+ Other methods will ignore it and instead should use the ``limit/offset``.
|
||||
+ PUT requests no longer return an error when this header is present (using limit/offset still triggers the error)
|
||||
|
||||
Thanks
|
||||
------
|
||||
|
||||
Reference in New Issue
Block a user