Marios Trivyzas

@DHRUV6029 Thx for your interest in contributing on this one. Please feel free to work on it and open a PR. But, regarding issue assignment, since long time now, we...

Using `psql` to connect to CrateDB yields the same wrong results: ``` crate=> create table t (a numeric(18,10)); CREATE 1 crate=> insert into t values (721330.4241866222::numeric(18,10)); INSERT 0 1 crate=>...

We could potentially also use the same logic for multiphase subselects: ``` matriv=# create table summits(mountain varchar(32)); CREATE TABLE matriv=# insert into summits values('Everest'), ('Mont Blanc'); INSERT 0 2 matriv=#...

Same goes for a normal check constraint, checking for null values: ``` cr> alter table test add b int check (b * 10 - 1 is not null); ALTER OK,...

if there is not a null check, CrateDB: ``` cr> alter table test add b int check (b * 10 - 1 > 2); ALTER OK, -1 rows affected (0.044...

There could be an option to also enable `DEFAULT` clause for adding columns, but this means all existing table rows need to be updated with this default value for the...

Let's also check the SQL spec about this one, before proceeding with the change.

Thx for reporting this @amotl . It has been fixed as a breaking change and it will be available with CrateDB `6.1`.

If we have the same behavior that we encountered here: https://github.com/crate/crate/pull/16843 I agree to go with strings.

and to be more precise, http streams the full number (reaches the client), but the `application/json` MIME type directive is the one that truncates digits.