Issue 99375 - silent conversion/overflow of values entered in the table data view, if they don't fit into the data range of the underlying table column
Summary: silent conversion/overflow of values entered in the table data view, if they ...
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: DEV300m38
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: usability
Depends on:
Reported: 2009-02-18 12:56 UTC by lars.langhans
Modified: 2017-05-20 10:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description lars.langhans 2009-02-18 12:56:19 UTC
Create a new table with a small integer and open this table by double click for

Insert the value 32769 into the small integer field which will result in -32767
value which is far away from the real value.

The expection sould be the biggest small int value if we overrun the maximun and
the smallest int value if we underrun the minimun.

Due to the fact it is dangerous I set this to Prio 2!
Comment 1 Frank Schönheit 2009-02-18 13:20:17 UTC
I don't see how changing 32769 to -32767 is more dangerous than changing 32769
to 32768 - in both cases, it is "data loss", if you want.

Also, I'm tempted to say that this is normally the task of the back-end, which
should not silently convert the data we pass to it. Depends a little bit on
whether the conversion happens when you leave the cell, or when the record is
committed to the database.

Having said that, I don't see a good solution. I don't think converting to the
maximum is better than overflow, and I don't think a modal message box when
leaving the cell is a good user experience.
Comment 2 Marcus 2017-05-20 10:44:17 UTC
Reset the assignee to the default "".