> To solve the problem of changing hash types, I suggest simply
> self-labeling the contents: "{sha1}hashvalue"
> and then down the road: "{sha4096}longerhashvalue"
> with some limited future-proofing by picking a reasonable length.
>
> Aaron
>
That doesn't sound too "relational" perhaps an extra column with "hash
type" as an enum? hard code the values into the code that deals with it.
Means you can avoid string parsing and you can do conversions from one
hash type to another "on the fly" easily.
Really to change hash should be minimal, read part and hash, update
table with new hash and hash type.
The down side I spose would be a largely redundant index. (IE people
generally aren't going to run multiple hashing types within one system)
Just a thought anyway.
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
