No need to index the Primary Key about storm HOT 5 CLOSED

Definitely. The ID is currently treated as any other key and we can easily optimize it by removing the useless call.

from storm.

But it should be optimized in the One method and not adding another method to learn.

from storm.

No it's all about optimization. If i remove the UniqueIndex on IDs on save, i will need to optimize One andAll.
They both access the indexes before getting from the bucket.

from storm.

Just commenting here even though it's a 4 years old issue because I can't seem to find the information elsewhere.
First of all, thanks @asdine for this project, it's truly awesome and makes working with bolt a breeze!
As of v3.2.0 I still have the __storm_index_ID which maps the ID with itself, which is clearly redundant. Is there something special to do to remove said index?

from storm.

It looks like this was fixed and then reverted with 68fc73b when the id tag was re-attributed an index. But maybe I'm out of touch with what's going on, I don't have the time to check all the commits and discussions regarding that. Is that index now required?
Changing f.Index = tagUniqueIdx to f.Index = "" removes the index associated with the ID. But I don't know if that will keep working as before.

from storm.