On 23 February 2010 20:25, Grary <[email protected]> wrote: > Another fine idea, it would appear. But why do both? Does checking a > combined parameters column before validation save me some kind of > performance hit? >
Yes it does a little... but you have to weigh up what hits are going to happen (performance or otherwise) if non-unique rows get in the table. If your job is on the line, then having an index across the fields is bullet proof, and processors are cheap... (ish) Being able to check "combined parameters" is just gravy - an added bonus that'll make the Rails coding simpler, but the index is what making *sure*. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
