Bolek Ziobrowski

Hi @Zahlii . Thanks for the pull request . It looks good but it would use more tests . The changes you pushed apply to to_str(date, format) and not to...

Hi @newskooler . The "workaround" for now is to use explicit order by clause with timestamp column as given in issue description : ```sql selecT * from test order by...

Excessive warnings can be disabled with: true Unfortunately there's no way to disable "no comment" only . The closes I found was : all,-missing but it also disables warnings about...

Probably the quickest way is to zip root dir and share :) In web console It's possible to export table schema by right clicking on table name (in tables list)...

Following rewrite takes 0.2s on 1mil-big table and uses ~ 100MB vs 1.2s and ~300MB for the original query . ```sql insert into weather_data_historical select cast(x*1000000000 as timestamp), to_str( cast(x*1000000000...

You can easily merge these rows into one with something like: ```sql select to_str( max( case when stat_name = 'warmest_day' then sensor_time else null end), 'yyyy') as warmest_day_year, max( case...

FYI, string_agg does work as a 'not-keyed' aggregate : ```sql select string_agg(s, ',') from tab; ``` but it doesn't work as 'keyed', e.g. ```sql select k, string_agg(s, ',') from tab...

No problem. Thanks for letting us now .

Hello @AllenEdison . I think this bug is fixed in 6.4.3 that was released last Friday. Please let me know if it's still an issue .

@stekman Could you explain the use case ? Prepared statements are normally optimized and planned once and then used multiple times . Tables and columns (I assume you don't mean...