From: Jim Burgess <jack.zelig@...>
Date: 2010-10-07T23:53:43+09:00
Subject: Re: Maximum length of array#hash

> While this answers your primary question, take care with storing a hash
> generated by the hash method.  Such methods are generally treated as a
> black box, so you can't be assured that different versions of Ruby, much
> less different implementations, will return the same hash given the same
> object.

Oh right, I didn't realize. I was just looking at what methods I could 
call on array and hash did exactly the job I wanted.

> Maybe this doesn't matter for your needs 
Nah, at the moment everything is working very smoothly. It is a small 
app and doesn't need to scale or move server.

> a = [1, 2, 3]
> Digest::MD5.hexdigest(a.to_yaml)
> # => "4088cb2d3462e59f1735319fa50747a0"
Thanks for that. I will have a look at using that instead.
Essentially all I want to do is create a hash-code out of an array.
If this is better practice and makes things less likely to break I will 
gladly use it.

> Like Robert said though, I'm not sure why you would want to store this
> kind of data in your DB in the first place.
So that I can compare current user input with the last successful user 
input.
This way I can eliminate double data submission.

Is there a better way to tackle double data submission?

Thanks for your reply,
Jim


-- 
Posted via http://www.ruby-forum.com/.