Ability to specify a whitelist of models to cache

[seangal2]

Hi,

Currently with the auto config you can specify excludedModels, and models which just override the settings.
I want to be able to enable the redis caching for just a specific set of models.

Could this functionality be added?
If so, I think I will start using this repo :)

Thanks!

[yxx4c]

Hi @seangal2,

Thank you for showing interest in the library! Adding this feature is certainly feasible. I will explore the possibility of implementing it without disrupting the existing functionality of AutoCacheConfig. However, I need to assess whether the benefits of this feature justify the programming effort, as there are already several ways to achieve similar results using the current options available in AutoCache and CustomCache.

[seangal2]

What are the current options to achieve this? My use-case is that we have cross language microservices, and I want to ensure that I only use caching for models that are not written to by python services for example. In order to make this future proof, I don't want to black list all the other models, since some developer can add a new model and not add it to the blacklist, potentially introducing cache inconsistencies. If I specify the models I want cached, it will be resistant to the addition of new models.

…

On Fri, Feb 21, 2025 at 11:29 AM caxxy ***@***.***> wrote: Hi @seangal2 <https://github.com/seangal2>, Thank you for showing interest in the library! Adding this feature is certainly feasible. I will explore the possibility of implementing it without disrupting the existing functionality of AutoCacheConfig. However, I need to assess whether the benefits of this feature justify the programming effort, as there are already several ways to achieve similar results using the current options available in AutoCache and CustomCache. — Reply to this email directly, view it on GitHub <#45 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALP3ZDRQUZRQB6J7WM5RU4T2Q3WX5AVCNFSM6AAAAABXQ6TYKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZUGAZTGMJZHE> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: yxx4c]*yxx4c* left a comment (yxx4c/prisma-extension-redis#45) <#45 (comment)> Hi @seangal2 <https://github.com/seangal2>, Thank you for showing interest in the library! Adding this feature is certainly feasible. I will explore the possibility of implementing it without disrupting the existing functionality of AutoCacheConfig. However, I need to assess whether the benefits of this feature justify the programming effort, as there are already several ways to achieve similar results using the current options available in AutoCache and CustomCache. — Reply to this email directly, view it on GitHub <#45 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALP3ZDRQUZRQB6J7WM5RU4T2Q3WX5AVCNFSM6AAAAABXQ6TYKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZUGAZTGMJZHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[yxx4c]

Hi @seangal2,

You can make use of the extended cache client in parallel with the default client. Use the cacheClient only when needed, and for everything else use the default client (without caching).