Georg Traar

Add datestyle session setting

1

## Summary of the changes / Why this improves CrateDB - Add `datestyle` session setting, _to allow `SHOW datestyle`_ - ~~Setting `datestyle` to the default value is allowed, but an...

Extend PRIVILEGES to follow Postgres RBAC

1

**Use case**: In the SQL standard, there is a clear distinction between users and roles, but this is not followed by PostgreSQL - PostgreSQL manages database access permissions using the...

`INSERT INTO SELECT` does not throw an error / warning when some inserts fail

7

### CrateDB version 4.6.8 / 4.7.0 ### Steps to Reproduce ```sql CREATE TABLE insert_into_source ( ts TIMESTAMP, ts_g TIMESTAMP); CREATE TABLE insert_into_sink ( ts TIMESTAMP, ts_g TIMESTAMP GENERATED ALWAYS AS...

**Use case**: Significantly improve the indexing and storage performance for geoshapes in CrateDB by using a simple to configure BKD-tree based indexing instead of complex to configure prefix tree based...

Support for first(returnField,searchField) and last(returnField,searchField) function

3

**Use case**: In timeseries use cases one might often want to get the latest or first value for a specific device/machine/thing. This can be achieved with sub-queries, which might become...

Support for named PRIMARY KEY constraints

1

**Use case**: PostgreSQL allows not only `CHECK` constraints, but also `PRIMARY KEY` constraints to be named. This is not totally obvious from the PostgreSQL docs [1], but is used by...

Support for `SHOW DateStyle;`

3

**Use case**: Postgres compatible tools like Datagrip, DBeaver, etc. want to get (and sometimes set e.g. Azure Data Studio) the **datestyle** used by the database. It seems like there is...

**Use case**: In PostgreSQL every table has several[ **system columns** ](https://www.postgresql.org/docs/14/ddl-system-columns.html)implicitly defined by the system. - tableoid - xmin - cmin - xmax - cmax - ctid Postgres compatible tools...

Support `HAVING` clause on selections without grouping (and with `UNNEST`)

1

**Use case**: Right now the `HAVING` keyword is only supported by `GROUP BY` or global aggregate queries. The SQL standard also allows `HAVING` without any grouping or without any grouping...

**Use case**: Jetbrains Datagrip using default PostgreSQL connector (i.e. not custom JDBC) Datagrip is running the following query on schema retrieval: ```sql select case when pg_catalog.pg_is_in_recovery() then null else pg_catalog.txid_current()::varchar::bigint...