Georg Traar

> as surname is not null, Django will ask us to back-fill it with a temporal default, to avoid null values. Default clause will only apply to new values in...

The `starts_with()` function has been [implemented](https://github.com/crate/crate/pull/17877). Optionally, the `^@` operator could be introduced in a follow-up. Since PostgreSQL does not support an `ends_with()` function, tools built for PostgreSQL are unlikely...

> How would end-users use this? > E.g. from a user perspective of crash, I'd still type SET xy = ... and expect that to work. > Similar with DB...

> Do you have a concrete example for where you need to query the information? Yes, this information is necessary to determine if an object needs to be transformed before...

Hi @FrancescoL96 Thank you for bringing this up. Currently, we don’t test or officially support OpenShift. There are no immediate plans to change this unless we see significant commercial demand....

The issue with PostgreSQL extensions appears to be primarily related to the use of `COPY FROM / TO stdin/stdout`, which is currently not supported in CrateDB. There is a ticket...

> By removing this limitation, we would block ourselves in introducing new internal system columns in future. This happened already once by e.g. introducing _seq_no and _primary_term. Without this restriction...

> If you don't see any other flaws that would block the release of the revamped documentation theme, we may be able to release it before heading into the summer...

Would it (in terms of latency) not be better to do this client-side? Using ANTLR4 and having the grammar/tokenizer ready would be rather language agnostic anyway. JS/TS wise modeDBA (https://modeldba.com/)...

Hi @Ben8t Thanks for sharing. From your point of view, what is the purpose of the added details, i.e., why would a user want to see these details in the...