You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A brief survey on Matrix suggests that we don't need time x is before time y phrasing and can do with time x is lesser than time y. This simplifies implementation, since under-the-hood we're using a simple x < y comparison. An alternative would have been to make up a mechanism for providing filter name aliases for when parameters match some pattern (like them being time-like).
Since the conversation in that Matrix channel has moved on, I'll comment here.
@dmos62 I think "21 January is less than 4 February" is not as intuitive for non-technical users, people don't regularly say that in English. I'd like to stick to the original phrasing.
Problem
This involves:
/api/v0/databases/<id>/types/
endpoint to store available filters on this typebetween
needs 2 parameters,is empty
needs 0)Additional context
sqlalchemy-filters
to provide filtering. See: https://github.com/centerofci/sqlalchemy-filters.TIMESTAMP
data type in the backend #424DATE
data type in the backend #425TIME
data type in the backend #426The text was updated successfully, but these errors were encountered: