Edit form is not "Save Changes" by default : Unique conflict
Issue #215
resolved
Originally reported on Google Code with ID 215
1. Create a table with a PK on one column (Integer for example)
2. Insert a row
3. Edit this row without modifying the PK
4. Submit the form by pressing enter from one of the inputs
The row should be updated and saved in the table.
But an error occurs saying the Primary Key must be UNIQUE.
Reason :
The form is built with 2 submit buttons, "Insert As New Row" and "Save Changes" - in
that order. HTML selects the first submit button when submitted via the enter key from
an input.
The action is actually seen as "Insert As New Row" but the PK is the same as the existing
one.
One solution would be to put the "Save Changes" first, and one might use CSS to make
it appear on the right in order to keep the same appearance (floating?).
Another solution would be to remove the "Insert As New Row" and replace it with a checkbox.
Reported by sherbrow1.0
on 2013-05-16 13:49:08
Comments (3)
-
-
This issue was closed by revision r429.
Reported by
crazy4chrissi
on 2013-12-24 22:53:21 - Status changed:Fixed
-
I simply switched positions of the two buttons. I think it is intuitive like this as well and not a big deal that the button positions are switched now.
Reported by
crazy4chrissi
on 2013-12-24 22:54:32 - Labels added: Target-1.9.5 - Log in to comment
Reported by
crazy4chrissi
on 2013-05-16 15:59:26 - Status changed:Accepted