What steps will reproduce the problem?
1. Create a database table with one or more fields with a maximum size.
2. Add a new record to that table. Forget how big the maximum field size is,
and try to add a longer string.
3. Try to save the record.
What is the expected output? What do you see instead?
In other similar interfaces, I'd expect the save attempt to fail, but for the
data I've just entered to remain on the screen - probably with the offending
field highlighted, so it's obvious what I need to put right before I can save.
In ORDS, you're returned to the table, and while you do get an error message
explaining what the problem was, you lose everything else you entered in the
Add New Record form, so have to go back and do it again. I can imagine this
being very annoying, especially if it's a table with lots of fields.
Additionally, there's nothing in the Add New Record form that indicates what
the field size limit is (or even that there is a limit). Showing this here
(perhaps in brackets after the field type, as in the schema designer) would
help reduce the risk of this happening.
Please use labels and text to provide additional information.
Original issue reported on code.google.com by meriel.p...@gmail.com on 1 Dec 2014 at 5:14
Original issue reported on code.google.com by
meriel.p...@gmail.comon 1 Dec 2014 at 5:14