Thread replies: 17
Thread images: 2
Thread images: 2
File: 1448127123275.jpg (122KB, 730x1100px) Image search:
[Google]
122KB, 730x1100px
If you have a key value storage, does it make sense to store the key value both ways, i.e.
action:date
and
date:action
so that you can search by both date or action very quickly (since the key is indexed).
The alternative is to loop the entire db if you're searching by value.
>>
>indexing by date
No, doesn't matter how you spin it. No.
>>
if you wanted to be able to quickly search the contents of items, you should have used something a little better than a hashtable
>>
>>51454643
Who is this bat twat?
>>
>>51454750
>not slugger chugger
>>
>>51454750
Sky Ferreira
Shitty indie pop singer
>>
>>51454701
Index by day then. So I can find out all the shit that happened on a certain day.
>>
>>51454735
The same problems still arises. Only one of the values is efficiently accessed.
>>
>>51454922
if only there were some sort of way to relationally store and query data items instead of sticking everything in a big dumb list
>>
>>51454897
enjoy your failure
>>
>>51454897
>index by day
Why not just index by modified Julian date into an array?
>>
What do /g/ think about Redis? Is it only useful for caching?
>>
>>51454786
Just listened to some of her stuff. Good lord is she bad.
>>
why don't you just use a sql database
>>
>>51454786
>>Shity indie pop singer
Don't you just mean indie music artist?
>>
>>51454643
OR you just use a real DBMS for what you are trying to do. It will save headaches in the long run.
>>
>>51454643
Isn't that the point of a key?
Something to search for?
Jesus Christ OP
Thread posts: 17
Thread images: 2
Thread images: 2