Skip to content

Releases: PostgREST/postgrest

v7.0.1

18 May 20:37
Compare
Choose a tag to compare

Fixed

Changed

  • From this version onwards, the release page will include a single Linux static executable that can be run on any Linux distribution.

v7.0.0

03 Apr 18:02
Compare
Choose a tag to compare

Added

  • #1417, Accept: application/vnd.pgrst.object+json behavior is now enforced for POST/PATCH/DELETE regardless of Prefer: return=representation/minimal - @dwagin
  • #1415, Add support for user defined socket permission via server-unix-socket-mode config option - @Dansvidania
  • #1383, Add support for HEAD request - @steve-chavez
  • #1378, Add support for Prefer: count=planned and Prefer: count=estimated on GET /table - @steve-chavez, @LorenzHenk
  • #1327, Add support for optional query parameter on_conflict to upsert with specified keys for POST - @ykst
  • #1430, Allow specifying the foreign key constraint name(/source?select=fk_constraint(*)) to disambiguate an embedding - @steve-chavez
  • #1168, Allow access to the Authorization header through the request.header.authorization GUC - @steve-chavez
  • #1435, Add request.method and request.path GUCs - @steve-chavez
  • #1088, Allow adding headers to GET/POST/PATCH/PUT/DELETE responses through the response.headers GUC - @steve-chavez
  • #1427, Allow overriding provided headers(Location, Content-Type, etc) through the response.headers GUC - @steve-chavez
  • #1450, Allow multiple schemas to be exposed in one instance. The schema to use can be selected through the headers Accept-Profile for GET/HEAD and Content-Profile for POST/PATCH/PUT/DELETE - @steve-chavez, @MahmoudKassem

Fixed

Changed

  • #1385, bulk RPC call now should be done by specifying a Prefer: params=multiple-objects header - @steve-chavez
  • #1401, resource embedding now outputs an error when multiple relationships between two tables are found - @steve-chavez
  • #1423, default Unix Socket file mode from 755 to 660 - @dwagin
  • #1430, Remove embedding with duck typed column names GET /projects?select=client(*)- @steve-chavez
    • You can rename the foreign key to client to make this request work in the new version: alter table projects rename constraint projects_client_id_fkey to client
  • #1413, Change server-proxy-uri config option to openapi-server-proxy-uri - @steve-chavez

v6.0.2

22 Aug 18:44
713b214
Compare
Choose a tag to compare

Fixed

  • #1369, Change raw-media-types to accept a string of comma separated MIME types - @Dansvidania
  • #1368, Fix long column descriptions being truncated at 63 characters in PostgreSQL 12 - @amedeedaboville
  • #1348, Go back to converting plus "+" to space " " in querystrings by default - @steve-chavez

Deprecated

  • #1348, Deprecate . symbol for disambiguating resource embedding(added in #918). The url-safe '!' should be used instead. We refrained from using + as part of our syntax because it conflicts with some http clients and proxies.

v6.0.1

31 Jul 00:30
Compare
Choose a tag to compare

Added

Fixed

  • #1336, Error when testing on Chrome/Firefox: text/html requested but a single column was not selected - @Dansvidania
  • #1334, Unable to compile v6.0.0 on windows - @steve-chavez

v6.0.0

21 Jun 21:23
dd86fe3
Compare
Choose a tag to compare

Added

Fixed

Changed

  • #1288, Change server-host default of 127.0.0.1 to !4

Deprecated

  • #1288, Deprecate . symbol for disambiguating resource embedding(added in #918). '+' should be used instead. Though '+' is url safe, certain clients might need to encode it to '%2B'.

Removed

  • #1288, Removed support for schema reloading with SIGHUP, SIGUSR1 should be used instead - @steve-chavez

v5.2.0

13 Dec 04:34
Compare
Choose a tag to compare

Added

  • #1205, Add support for parsing JSON Web Key Sets - @russelldavies
  • #1203, Add support for reading db-uri from a separate file - @zhoufeng1989
  • #1200, Add db-extra-search-path config for adding schemas to the search_path, solves issues related to extensions created on the public schema - @steve-chavez
  • #1219, Add ability to quote column names on filters - @steve-chavez

Fixed

v5.1.0

02 Sep 13:46
Compare
Choose a tag to compare

Added

Fixed

Changed

  • #1099, Numbers in json path ?select=data->1->>key now get treated as json array indexes instead of keys - @steve-chavez
  • #1128, Allow finishing a json path with a single arrow ->. Now a json can be obtained without resorting to casting, Previously: /json_arr?select=data->>2::json, now: /json_arr?select=data->2 - @steve-chavez
  • #724, Change server-host default of *4 to 127.0.0.1

Deprecated

  • #724, SIGHUP deprecated, SIGUSR1 should be used instead

v0.5.0.0

15 May 04:20
Compare
Choose a tag to compare

Added

  • The configuration (e.g. postgrest.conf) now accepts arbitrary settings that will be passed through as session-local database settings. This can be used to pass in secret keys directly as strings, or via OS environment variables. For instance: app.settings.jwt_secret = "$(MYAPP_JWT_SECRET)" will take MYAPP_JWT_SECRET from the environment and make it available to postgresql functions as current_setting('app.settings.jwt_secret'). Only app.settings.* values in the configuration file are treated in this way. - @canadaduane
  • #256, Add support for bulk UPSERT with POST and single UPSERT with PUT - @steve-chavez
  • #1078, Add ability to specify source column in embed - @steve-chavez
  • #821, Allow embeds alias to be used in filters - @steve-chavez
  • #906, Add jspath configurable role-claim-key - @steve-chavez
  • #1061, Add foreign tables to OpenAPI output - @rhyamada

Fixed

Changed

  • #828, A SET SCHEMA <db-schema> is done on each request, this has the following implications:
  • To use RPC now the json_to_record/json_to_recordset functions are needed, these are available starting from PostgreSQL 9.4 - @steve-chavez
  • Overloaded functions now depend on the dbStructure, restart/sighup may be needed for their correct functioning - @steve-chavez
  • #1098, Removed support for:
    • curly braces {} in embeds, i.e. /clients?select=*,projects{*} can no longer be used, from now on parens () should be used /clients?select=*,projects(*) - @steve-chavez
    • "in" operator without parens, i.e. /clients?id=in.1,2,3 no longer supported, /clients?id=in.(1,2,3) should be used - @steve-chavez
    • "@@", "@>" and "<@" operators, from now on their mnemonic equivalents should be used "fts", "cs" and "cd" respectively - @steve-chavez

v0.4.4.0

09 Jan 03:52
Compare
Choose a tag to compare

Added

Fixed

v0.4.3.0

06 Sep 16:35
Compare
Choose a tag to compare

Added

Fixed

Changed