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 }}
This repository has been archived by the owner on Feb 3, 2023. It is now read-only.
it's just adding a local index for each stored EAV to EAVI so we can get the "current" value for any given EA
if the data is added on the way in then IIRC it should be easy enough to get the right value with the existing iterators
long term it might be worth adding a new method to the eav storage trait so that implementations can optimise this lookup, e.g. with indexes and sorting on the backend
but for now why not just stick this logic in rust?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@thedavidmeister said...
it's just adding a local index for each stored EAV to EAVI so we can get the "current" value for any given EA
if the data is added on the way in then IIRC it should be easy enough to get the right value with the existing iterators
long term it might be worth adding a new method to the eav storage trait so that implementations can optimise this lookup, e.g. with indexes and sorting on the backend
but for now why not just stick this logic in rust?
The text was updated successfully, but these errors were encountered: