-
I keep coming back to JSONiq because it's such an elegant language, and it would be cool if I could use it for an api instead of eg. GraphQL. There's Hasura and similar for the latter that auto genera…
-
Our current codebase on stats endpoints run all time computations as and when an API call is made and all these operations are performance heavy on RDS. I propose to pick some best practices from Miss…
-
```
What new feature would you like to see implemented? How will you use it?
It would be great if you could map off aggregates.
-----------------------------------------------------------------------…
-
Currently, if any data was to be stored in the db, it is stored similar to how a normal postgresql db would store information. By introducing [Hypertables](https://docs.timescale.com/use-timescale/lat…
-
## Core problem
It is currently hard to discover the different kinds of entities available in a chart.
For example, it is unclear at first sight that "special" entites and groupings like "Africa",…
-
| | |
| --- | --- |
| Bugzilla Link | [42642](https://llvm.org/bz42642) |
| Version | unspecified |
| OS | All |
| Reporter | LLVM Bugzilla Contributor |
| CC | @dwblaikie,@DougGregor,@zygoloi…
-
It seems like UNION operator are not supported in continuous aggregates yet. In the meantime, is there any workaround that is performant?
-
Currently aggregates and the available keys are handled in the config reader. Instead they should be configurable in the json.
-
### Feature Description
In the [get_aggregates_for_payments](https://github.com/juspay/hyperswitch/blob/dccb8d4e629d615a69f6922a96e72f10d3410bfc/crates/router/src/core/payments.rs#L3249) function, …
-
Currently the `HAVING` clause translation takes into account only aggregations - however when dealing with subqueries, fields can be used as well:
```
SELECT * FROM (
SELECT languages, COUNT(*)…