Redis as db

[ErikKristiansen96]

/### Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

Describe the solution you'd like

When importing a json or dictionary into Set (encoded as byte[]) it should be saved for each key in the json and not as one big string in the "data" field.
An example is shown in attachment "old" vs "new".
Accessing different fields should be faster than returning the entire string.
If the json is a list then the key should be taken from each json object the first element.

Additional context

I have already implemented it on my fork, if that is of any interest
Old:

New:

If Json is a list take first value as id:

[ajcvickers]

@ErikKristiansen96 What do you mean by "Set"?

[ErikKristiansen96]

@ajcvickers I mean the function "Set" in the RedisCache.cs class. Maybe I should have written: when using the library to save any kind of data in a Redis cache it is always saved as one big string (as seen in the "old" picture). I'd like the possibility to save my data in smaller subkeys (as seen in the other two pictures).
To put it into Redis commands: Instead of HSET <KEY> data <MY_DATA> I would like to HSET <KEY> <FIELDKEY1> <SPLIT_DATA1> <FIELDKEY2> <SPLIT_DATA2> ...

[mitchdenny]

@ErikKristiansen96 the RedisCache isn't really designed to be a general data access layer. It implements IDistributedCache which presents a consistent interface across a range of data stores that can be plugged into ASP.NET for various purposes.

If you want to use Redis as a more generic data store outside of the scope of what we've designed the IDistributedCache interface around you might want to consider using the StackExchange.Redis client directly which will give you all the flexiblity you like (it is what we use internally for RedisCache).

Hi @ErikKristiansen96. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.