Grouper Developers Forum

[David Langenberg <>]

----- "Chris Hyzer" 
<>
 wrote:

> That is also an option, thanks.  I don’t see this issue in Jira, is
> there an issue number?
> If we really care that it is unique, this might not work since
> multiple inputs can hash to the same value, so I would lean toward one
> of the previous options... but if those aren’t ok, then this would be
> better than now I guess

Well, your constraint is on the triplet group_id, field_name, hash_value so 
collisions shouldn't happen anymore than they do now.  If you're referring to 
the MD5/SHA1 specific collision issues you're chances of a random collision 
(sha1) are about 1 in 9 quintillion.  You've got a better chance of winning 
the lottery and being hit with lightning than getting a random collision.  
Attacks are another thing, but honestly, if someone with malicious intent is 
in your RDBMS and able to exploit what should be a private, unexposed column 
by the API, via direct SQL you've got bigger problems.

Dave

-- 
***********************************************************
David Langenberg
Network Based Services
The University of Chicago
***********************************************************