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
{{ message }}
Repository navigation
Allow date, datetime, time for ge, gt, le, lt #482
Out of curiosity, do these constraints need to be implemented for each type? I was looking over the list of supported types and realized decimals, strings and UUIDs can be compared as well, and just about anything that implements the comparison magic methods.
Currently yes. For ints/floats a type-specific implementation can be much more efficient than a generic one.
For more complicated types like uuids/decimals/... there may be negligible benefits for implementing them in native code; we might be better served by using a generic implementation here.
Activity
jcrist commentedon Jul 13, 2023
Thanks for opening this, this is definitely a feature that makes sense to add. Tossing it on the todo list.
alexei commentedon Jul 13, 2023
Out of curiosity, do these constraints need to be implemented for each type? I was looking over the list of supported types and realized decimals, strings and UUIDs can be compared as well, and just about anything that implements the comparison magic methods.
jcrist commentedon Jul 13, 2023
Currently yes. For ints/floats a type-specific implementation can be much more efficient than a generic one.
For more complicated types like uuids/decimals/... there may be negligible benefits for implementing them in native code; we might be better served by using a generic implementation here.
FHU-yezi commentedon Jan 22, 2025
Wonder this feaature become true.