Niklas Schmidtmer

Results 29 issues of Niklas Schmidtmer

**Use case**: For time-series use cases, there is frequent usage of `generate_series` to e.g. generate time buckets and then joining a larger table with sensor data. Example: ```sql SELECT s.time_bucket,...

feature: performance
feature: sql: joins
complexity: no estimate
needs upvotes
need refined description

**Use case**: In case a 3rd party tool runs into any kind of error while executing an SQL statement, a `ROLLBACK` is often performed by the tool as a reaction...

feature: pgsql
feature: integration
complexity: no estimate
needs discussion
needs upvotes
tool: Dataiku

### Problem Statement There are a few `INTERVAL` values that work in PostgreSQL, but not in CrateDB: ```sql postgres=# SELECT '1s'::INTERVAL; interval ---------- 00:00:01 (1 row) postgres=# SELECT '1m'::INTERVAL; interval...

contributions welcome
feature: sql: type system
complexity: 1-3
tool: Grafana

### Problem Statement PostgreSQL has a [COMMENT](https://www.postgresql.org/docs/current/sql-comment.html) functionality that allows adding textual comments on several types of entities in the database. Those comments can increase usability for users by providing...

enhancement
complexity: no estimate
need refined description

### CrateDB version 5.3.0 ### CrateDB setup information _No response_ ### Problem description Table names in `sys.snapshots`'s `tables` array column aren't quoted, making it hard to use its values. ###...

feature: ux
complexity: no estimate

### Problem Statement PostgreSQL supports an optional `precision` parameter as part of the `timestamp`/`time`/`interval` data types: ```sql postgres=# SELECT NOW()::TIMESTAMP(0); now --------------------- 2023-11-16 08:57:47 (1 row) postgres=# SELECT NOW()::TIMESTAMP(1); now...

feature: sql: type system
complexity: no estimate

### Problem Statement PostgreSQL's [DELETE statement](https://www.postgresql.org/docs/current/sql-delete.html) supports a `RETURNING` clause. CrateDB currently supports `RETURNING` for `UPDATE`, but not for `DELETE`. A use case behind that can be to synchronize data...

contributions welcome
feature: sql: query extension
complexity: no estimate

### Problem Statement When debugging performance issues, the `EXPLAIN ANALYZE` output is typically investigated. One of the questions regularly is to understand which partitions or shards have been accessed, for...

feature: diagnostics
contributions welcome
complexity: 3-5

### Problem Statement **Multi-tenancy scenario with one shared table** Given a multi-tenant table that is implemented as `CREATE TABLE data (customer_id INTEGER, data INTEGER);`. An application queries data from that...

complexity: no estimate
needs discussion
needs upvotes
feature: administration

In situations when shards cannot be allocated and a table/partition shows a yellow/red state, it is difficult for users to troubleshoot the reason with information shown in the Admin UI....

feature
contributions welcome
complexity: no estimate
feature: shards