This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Somewhat a bug. Mostly a usability issue Was getting a strange result in my application from what seemed to be a phantom row in the database left over from debugging. When I queried the table using the SQL explorer it wasn't showing the odd row. Turns out the SQL Explorer was showing the error (which I didn't notice at first) 'Error code 0, SQL state 22003: '4.294967295E9' in column '2' is outside valid range for the datatype INTEGER.' and not displaying any information about the row at all. Had to use a different tool to find the offending row and modify it. Would be nice if it output the row in the main list, and allowed me to modify it there (showing the error message below) Or made the error message include the index of the row so I would have the information to construct a sql query to modify it. WinXP MySQL 5.0.51a jdbc connector used on mysql://localhost:3306
Created attachment 74112 [details] An example table with an out of bounds value
Reassigned to new owner.
Ok - Problem: the db reported datatype integer, it was forgotten, that some databases support unsigned datatypes, than a DB integer does not fit into a java integer in this case: Real Value: 4294967295 Integer.MAX_VALUE: 2147483647 With the change from 239274 netbeans detects this and switches to a long value. *** This bug has been marked as a duplicate of bug 239274 ***