Jonathan Gray
Jonathan Gray
A legit reason to use **kwargs? 😲 I like this idea _but_ I think it would break the hashing of custom query, so we'd need a different solution there.
Expanding on the above - custom query hashing is dependent on being able to normalise the input SQL, which we do by parsing it against the PostgreSQL parser. Obviously that's...
I was thinking about this in the context of flowmachine over the weekend. One key thing that would need to happen to allow us to make db connections fully async...
Relates to #173
SQLAlchemy is now async friendly, so this is less of a stretch now.
This post on the pg-development group has a minimal window function implementation: https://www.postgresql.org/message-id/[email protected] which is a decent reference.
Also relevant, is this PR against PostGIS which added the DBSCAN window function: https://github.com/postgis/postgis/pull/86
Other options on the return type might be a json blob, a composite type, or a custom type.
Or maybe in rust, @Thingus?
Blocked by: - https://github.com/facebook/create-react-app/issues/11565