Does a string hash exist which can ignore the order of chars in this string? Eg."helloword" and "wordhello" can map into the same bucket.
相关问题
- facebook error invalid key hash for some devices
- Change first key of multi-dimensional Hash in perl
- Bool.hashValue valid to convert to Int?
- Is the c++ hash function reasonably safe for passw
- Reliably reproduce in C# a legacy password hashing
相关文章
- Bcrypt vs Hash in laravel
- What is the fastest way to map group names of nump
- Finding out whether there exist two identical subs
- Oracle STANDARD_HASH not available in PLSQL?
- Looking for a fast hash-function
- Python: Is there any reason *not* to cache an obje
- C# how to calculate hashcode from an object refere
- How Docker calculates the hash of each layer? Is i
If you don't mind strings like "ac" and "bb" generating the same hash value, you can add the values of the characters together. (a + b + c is equal to a + c + b.)
If you want to reduce the possibility of hash code collisions of that kind, then you can multiply the values of the characters together. (a * b * c is also equal to a * c * b.)
If that's not good enough either, then you can sort all the characters in the string before applying the default string hashing function offered to you by whatever language it is that you are using. (So, both "helloword" ad "wordhello" would become "dehlloorw" before hashing, thus generating the same hash code.)
Although the other suggestions of multiplying or adding characters would work, notice that such a hash function is not secure at all.
The reason is that it will introduce a ton of collisions and one of the main properties a hash function has is the low probability of collisions.
For example, a + b + c is the same as c + b + a. However, it is also the same as a + a + d (since the sum of the ascii characters are the same). The same thing applies for multiplying or xor-ing the numbers.
In sum, if you want to achieve a hash function which ignores order, you can but it will introduce a ton of collisions which will potentially make your program faulty and insecure.