(I thought that this was already a tracked issue, but I cannot find it.)

See https://github.com/simdjson/simdjson/blob/c5def8f7060a7e9519c7f38e2c4ddf2dc784d6a8/doc/basics.md#json-pointer

If the pointer points at an array or an object, you'd like to be able to do...

    auto doc = parser.iterate(json);
    for (auto x : doc.at_pointer(insert json pointer expression)) {
     
 

Our users are often confused by the output from programs such as zip2john sometimes being very large (multi-gigabyte). Maybe we should identify and enhance these programs to output a message to stderr to explain to users that it's normal for the output to be very large - maybe always or maybe only when the output size is above a threshold (e.g., 1 million bytes?)

Create

create table tt (dts timestamp, nts timestamp) timestamp(dts)

Insert

insert into tt 
select timestamp_sequence(1577836800000000L, 10L), timestamp_sequence(1577836800000000L, 10L) 
from long_sequence(2L)

Select

select 'nts', min(nts) from tt where nts > '2020-01-01T00:00:00.000000Z'

Expected
nts in the first column

Actual
timestamp

Examples from simd-everywhere/simde#685

SIMDE_FLOAT32_C(-2147483650.0)
SIMDE_FLOAT32_C( 2147483649.0)

SIMDE_FLOAT64_C(-2147483650.0)
SIMDE_FLOAT64_C( 2147483649.0)

The procedure is:

1. Find tests that use SIMDE_FLOAT32_C or SIMDE_FLOAT64_C in their test_vec
2. Copy-n-paste an entry in the test_vec, modifying the inputs using the overflow valu

It might be worth considering adding simd-json to the TechEmpower benchmarks:

https://github.com/TechEmpower/FrameworkBenchmarks/blob/cfbbf5d11143c96851620eb1aeaf3c2893e862c9/frameworks/Rust/actix/src/main.rs#L23

To make this really worthwhile #121 would be good.

suggested by @pickfire