11.0.1
======

These release notes include the changes in versions `11.0.0 <https://github.com/PostgREST/postgrest/releases/tag/v11.0.0>`_ and `11.0.1 <https://github.com/PostgREST/postgrest/releases/tag/v11.0.1>`_. The detailed changelog and pre-compiled binaries are available on the `GitHub release pages <https://github.com/PostgREST/postgrest/releases>`_.

Features
--------

Transactions
~~~~~~~~~~~~

- New configurable :ref:`isolation_lvl`.
- New :ref:`impersonated_settings`.

Inserts
~~~~~~~

- New :ref:`bulk_insert_default`.

Functions
~~~~~~~~~

- Filters on Table-Valued Functions are now guaranteed to be inlined. See :ref:`function_inlining`.

Horizontal Filtering
~~~~~~~~~~~~~~~~~~~~

- New ``isdistinct`` :ref:`operator <operators>`. It is a direct translation of `IS DINTINCT FROM <https://www.postgresql.org/docs/current/functions-comparison.html#FUNCTIONS-COMPARISON-PRED-TABLE>`_.
- New ``and/all`` :ref:`modifiers`.

Resource Embedding
~~~~~~~~~~~~~~~~~~

- New :ref:`top_level_order`.
- New :ref:`spread_embed`.
- New :ref:`null_embed`.
- New :ref:`empty_embed`.

OpenAPI
~~~~~~~

- Allow :ref:`overriding the OpenAPI title <open-api>`.
- Allow :ref:`override_openapi`.

Admin
~~~~~

- New :ref:`trace_header`.

Documentation improvements
~~~~~~~~~~~~~~~~~~~~~~~~~~

- New :ref:`transactions` reference.
- New :ref:`connection_pool` reference.
- Split :ref:`api` into other sub-references.
- Split :ref:`authn` into :ref:`db_authz` and :ref:`sql_user_management`.
- Split :ref:`admin` into :ref:`intgrs`, :ref:`nginx` and :ref:`connection_pool`.

Bug fixes
---------

- Please check the "Fixed" section on https://github.com/PostgREST/postgrest/releases/tag/v11.0.0 and https://github.com/PostgREST/postgrest/releases/tag/v11.0.1.

Breaking changes
----------------

- 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
------

Big thanks from the `PostgREST team <https://github.com/orgs/PostgREST/people>`_ to our sponsors!

.. container:: image-container

  .. image:: ../_static/cybertec-new.png
    :target: https://www.cybertec-postgresql.com/en/?utm_source=postgrest.org&utm_medium=referral&utm_campaign=postgrest
    :width:  13em

  .. image:: ../_static/2ndquadrant.png
    :target: https://www.2ndquadrant.com/en/?utm_campaign=External%20Websites&utm_source=PostgREST&utm_medium=Logo
    :width:  13em

  .. image:: ../_static/retool.png
    :target: https://retool.com/?utm_source=sponsor&utm_campaign=postgrest
    :width:  13em

  .. image:: ../_static/gnuhost.png
    :target: https://gnuhost.eu/?utm_source=sponsor&utm_campaign=postgrest
    :width:  13em

  .. image:: ../_static/supabase.png
    :target: https://supabase.com/?utm_source=postgrest%20backers&utm_medium=open%20source%20partner&utm_campaign=postgrest%20backers%20github&utm_term=homepage
    :width:  13em

  .. image:: ../_static/oblivious.jpg
    :target: https://oblivious.ai/?utm_source=sponsor&utm_campaign=postgrest
    :width:  13em

* `Roboflow <https://github.com/roboflow>`_
* Evans Fernandes
* Jan Sommer
* `Franz Gusenbauer <https://www.igutech.at/>`_
* Zac Miller
* Tsingson Qin
* Michel Pelletier
* Jay Hannah
* Robert Stolarz
* Nicholas DiBiase
* Christopher Reid
* Nathan Bouscal
* Daniel Rafaj
* David Fenko
* Remo Rechkemmer
* Severin Ibarluzea
* Tom Saleeba
* Pawel Tyll

If you like to join them please consider `supporting PostgREST development <https://github.com/PostgREST/postgrest#user-content-supporting-development>`_.