Jaromir Hamala

I sent a PR to Telegraf: https://github.com/influxdata/telegraf/pull/14158

hello @badrbouslikhin, we are trying something slightly different. It's not released yet, but here is a little teaser: If you start the latest QuestDB snapshot (either build it yourself from...

after talking to @ideoma I'm going with: ```sql create table with (batch=1000, maxo3lag=1000) as (select ..... ) timestamp(ts) partitioned by day; ```

thanks @superichmann for reporting the issue and for the reproducer. I used your reproducer to create a simpler one: ```sql select coalesce(1/n, 0) from ( select 0::double as n from...

ok, it's not due to typecasting. I assume you are using the REST interface. Is that so? Here is what is going on: - Floating point division by `0` results...

hello @superichmann, I'm not sure I understand your last message. You can work with `double` (and thus `Infinity`) in all layers of your query. You only cast from double to...

well, that's the limitation of the JSON format. It does not allow numeric values which cannot be represented as sequences of digits. so there is no good option here -...

that looks like an intentional change: https://github.com/questdb/questdb/pull/2557 > change to_timestamp(S) to always interpret arg as micros. Similar function in PG interprets string as double, where scale values used for millis...

@ideoma in fact the single parameter is documented. see: https://questdb.io/docs/reference/function/date-time/#to_timestamp > Note that conversion of ISO timestamp format is optional. QuestDB automatically converts string to timestamp if it is a...

good point, I misinterpreted the paragraph, my bad.