Support aggregations over TIMESTAMP WITHOUT TIMEZONE fields?

[jlowin]

Hello,

At the moment it appears that aggregations over datetime fields (timestamps) are not supported -- querying the maximum timestamp, for example. Are there plans to add support for these pseudo-numeric types (or am I looking in the wrong place?)

Thanks!

[coco98]

@0x777 @rakeshkky Thoughts?

[0x777]

Yes. We'll add support for this very soon.

[0x777]

@jlowin This already works for timestamp and date columns. Can you give us the table schema where this doesn't work?

[jlowin]

@0x777 I apologize for the delayed reply. The columns that weren't working were typed as "timestamp without timezone"; when I changed them to "Timestamp" in the Hasura console, therefore converting them to "timestamp with timezone" (timestampz), it worked as described. Hasura's timestamp functionality has otherwise been perfect for these columns.

[CTOJoe]

I just ran into this issue. It does not seem to be resolved yet. If I have a column with type "timestamp without timezone". When querying the aggregate, the max and min is missing for the column. If I change the column to type "timestamp with timezone" the max and min aggregate is available.

Here is the column I set to with timezone.

Here is the available aggregate fields

Here is the type changed to "timestamp without time zone"

The created_at aggregate disappears once the type is changed.

[mrgusev]

Any updates on this issue? I just got the same problem on the latest beta release.