We occasionally have a user pressing “submit” button more than once.
I know I can disable submit button using “onclick”.
But I sometimes need a more solid solution especially
for a form that could change a record inside the database.
What could be the best way to solve the problem?
I need to access to the existing database record first and
compare the record with a new coming record.
I am now thinking about checking almost all attributes.
Assuming this is a simple blog, I would check the title
and post for exact match.
I was trying to find an open source Rails app to have
a solution, do you know any?
If I’m following you correctly, check out the RailsSpace book site.
You can download the final application. In the application, look at
the comments conroller in the create action. He’s checking for
duplicates and throwing them out if so.
If you are updating any state or flag on first submit; you can possibly
generate an exception if that flag is already set and second submit
tries to
set it again. Then you can catch it (rescue) and ignore or display the
error/message accordingly.
