> validates_associated
> validates_each
These two just aggregate other validations
> validates_length_of # esp if a text value is being appended to
save always provides the full value of every column, there's no way
you can be 'appending' and using active record's save.
> i'd vote for sticking
>
> def transaction options = {}
> end
>
> thoughts?
This definitely sounds like a long term option to consider, assuming
the terminology and api can be unified across all the databases etc.
> btw - we had this happen three times today. the culprit was submit
> button that is not disabled after the first click and people were
> double clicking it out of habbit - thus two requests come in quite
> close together. js can solve it, but i'm not comfortable maintaining
> db integrity via js ;-)
Stick a unique index on the field and you'll be fine.
>
>
> a @ http://codeforpeople.com/
> --
> we can deny everything, except that we have the possibility of being
> better. simply reflect on that.
> h.h. the 14th dalai lama
>
>
>
>
> >
>
--
Cheers
Koz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---
