feat: add limited delete

CHANGELOG.md

@@ -18,7 +18,7 @@ This project adheres to [Semantic Versioning](http://semver.org/).
    + #1689, Add the ability to run without `db-anon-role` disabling anonymous access. - @wolfgangwalther
  - #1543, Allow access to fields of composite types in select=, order= and filters through JSON operators -> and ->>. - @wolfgangwalther
  - #2075, Allow access to array items in ?select=, ?order= and filters through JSON operators -> and ->>. - @wolfgangwalther
- - #2156, Allow applying `limit/offset` to UPDATE to only affect a subset of rows - @steve-chavez
+ - #2156, Allow applying `limit/offset` to UPDATE/DELETE to only affect a subset of rows - @steve-chavez
    + Uses the table primary key, so it needs a select privilege on the primary key columns
    + If no primary key is available, it will fallback to using the "ctid" system column(will also require a select privilege on it)
    + Will work on views if the PK(or "ctid") is present on its SELECT clause
@@ -47,7 +47,7 @@ This project adheres to [Semantic Versioning](http://semver.org/).
 
  - #2001, Return 204 No Content without Content-Type for RPCs returning VOID - @wolfgangwalther
    + Previously, those RPCs would return "null" as a body with Content-Type: application/json.
- - #2156, `limit/offset` now limits the affected rows on UPDATE  - @steve-chavez
+ - #2156, `limit/offset` now limits the affected rows on UPDATE/DELETE  - @steve-chavez
    + Previously, `limit/offset` only limited the returned rows but not the actual updated rows
 
 ## [9.0.0] - 2021-11-25