pkoppstein

@delip - Since you have a big JSON dump, you are presumably reading it in as a file. In that case, from what you write, it would seem that the...

@nicowilliams - No doubt I'm missing something, but using @dequis's test case, it seems this change entails a step backwards: ``` github/nicowilliams/jq$ ./jq --version jq-1.2-889-gb28c886 github/nicowilliams/jq$ git log -1 commit...

@kryonix - Thanks for your workaround. It works, but the variant of the original program shown below produces bogus results even though all the formal parameter names have been made...

@kryonix wrote - > Oh shoot Aha. I should have been able to infer that from the sensitivity to random(). Do you know whether the perilous semantics of DuckDB MACRO...

This is to confirm that jaq (including jaq 2.0.0-alpha) is incorrect: ``` $ cat bananaman.json "\u200bbanana \u200eman" $ jq -r . bananaman.json | jq -R . | jaq . "\u{200b}banana...

1. The SELECT query results can be reproduced on a Mac e.g. using v1.0.1-dev4226. 2. These results are evidently the consequence of implicit type conversions induced by `=`; for example,...

In the hope that this `issue` will not automatically be closed, let me ask whether it would be too much to hope for DuckDB to support an operator with the...

@soerenwolfers - https://github.com/duckdb/duckdb/issues/15060 seems to be about the overzealousness of equality-induced casting, which is distinct from the proposal mentioned above to introduce an operator for strict equality. Should there be...

@Maxxen. OK, but that was not a very helpful error message. I'll edit the "subject".

@Maxxen wrote: > what else would the error message be? The current error message certainly seems erroneous as it refers to "fn" as a column, whereas it is a formal...