Reverse fingerprint storage in database
Bug #1128565 reported by
Casey Marshall
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| hockeypuck |
Fix Released
|
High
|
Casey Marshall | ||
Bug Description
This is a database optimization for MongoDB, but probably also applies to RDBMS, as the LIKE operator also "likes" a leading prefix...
Store the public key fingerprint in reverse order, least-significant hex nibble to most-significant hex nibble, left-to-right. This way, short ID and long key ID search can both use the same rfingerprint field.
This eliminates two indexes in MongoDB, and also consolidates key identifiers, removing the potential for them to get out of sync.
Related branches
| Changed in hockeypuck: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
