Same result for different numbers

[anstapol]

Hi there, I'm using the library on a Laravel project to generate a string counterpart of the model unique identifier (integer).

I successfully used it on one model but now having conflicts with another one as you can see on the screenshot.

Am I missing something?

[vinkla]

K and k are different characters.

[anstapol]

omg, so stupid of me I'm sorry. Had it saving to the MySQL database which is not considering the casing for the unique constraint 🤦‍♂️

thank you @vinkla!

btw I've noticed that in the docs the recommended PHP library is https://github.com/sqids/sqids-php is that repo going to eventually replace this one?

[vinkla]

omg, so stupid of me I'm sorry. Had it saving to the MySQL database which is not considering the casing for the unique constraint 🤦‍♂️

Don't recommend saving the hashed IDs in the database.

btw I've noticed that in the docs the recommended PHP library is https://github.com/sqids/sqids-php is that repo going to eventually replace this one?

Sqids is a successor but Hashids isn't going anywhere.

[anstapol]

Don't recommend saving the hashed IDs in the database.

why not?

[miquelfire]

HashIDs (And Sqids) are meant to hide the real number used for the PK. So the database will have a number ID (1, 40, 200, etc.), but the end user will see the results of encoding to HashIDs in the URL, for example.