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
There are some use cases where the redis endpoint has read and write endpoints. It will be beneficial to support different endpoints for read queries and write queries. I have looked through the code and it looks like that AbstractModel can be patched so get_store() returns different model based on the query type. Do you consider this as something that can be achieved by the library ?
The text was updated successfully, but these errors were encountered:
Thanks @dimitarq for your interest to contribute. From the sounds of it, such a feature seems beyond the simplistic scope of this library.
However, if it can be pulled off by inheritance from AbstractStore, AsyncStore, Model or/and AbstractModel etc., you could share it here as a recipe for other users who might have similar use cases.
There are some use cases where the redis endpoint has read and write endpoints. It will be beneficial to support different endpoints for read queries and write queries. I have looked through the code and it looks like that AbstractModel can be patched so get_store() returns different model based on the query type. Do you consider this as something that can be achieved by the library ?
The text was updated successfully, but these errors were encountered: