javier ramírez

Two issues here: timestamp format and table name ## timestamp format With the new proposed changes at https://github.com/questdb/questdb.io/pull/967, docs on importing look way better. But I believe there are still...

As an example of how this works using standard SQL with analytical functions see https://cloud.google.com/bigquery/docs/reference/standard-sql/functions-and-operators#percentile_cont

This is the left table (55M rows) ``` CREATE TABLE 'so_posts' ( AcceptedAnswerID INT, AnswerCount INT, ClosedDate TIMESTAMP, CommentCount INT, CommunityOwnedDate TIMESTAMP, CreationDate TIMESTAMP, FavoriteCount INT, Id INT, LastActivityDate TIMESTAMP,...

For inspiration check https://stackoverflow.com/questions/73959230/how-to-use-touch-functions

As per Amy's suggestion, we can add some story here to illustrate how this could be used. Since we are using the taxi rides dataset, we could have the following:...

String_agg now works with keyd groups, but string_agg(distinct col) is not supported just yet, so re-opening this to be able to track. Renamed the issue to make it specific

ugly potential workaround for the time being ``` SELECT timestamp, first(price) AS open, last(price) AS close, min(price), max(price), sum(amount) AS volume FROM trades WHERE symbol = ‘BTC-USD’ AND timestamp >...

related to https://github.com/questdb/questdb/issues/2995

For context, the pandas docs on indices for time-series. I see them very often specially when doing downsampling or filling gaps in your data (equivalent to questdb's FILL)

Also, when using a named index, I would expect the designated timestamp column in QuestDB to retain the name. Otherwise when I have to use the column in a select...