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.
[ BUILD # : 200509151455 ] [ JDK VERSION : 1.5.0 ] The function in the database command shell to copy data result from queries only copies the part that is visible in the window table cell. Correct operation would be to copy the full result of the query (for that row/cell), even if it is too large to fit in a cell. The existing functionality is effectively unable to copy large cell values, for instance blog entries, xml data, files / blobs etc.
A few comments: 1. this is as designed, making this issue more an enhancement. 2. since only a part of the data is retrieved from the ResultSet when displaying, it requires support for scrollable ResultSets. The WebLogic driver for MS SQL Server doesn't support them (at least the version we are testing with). But this isn't an issue, the action would be supported only with drivers supporting scrollable RSs. 3. "copy to clipboard" for large fields and/or many rows is likely to cause out of memory errors. Wouldn't it be better to implement a new action for saving cells/rows to (a) file(s)?
Follow-up: 1. Maybe this is as designed, it was still confusing. The virtually identical utility that comes along with Hsql (org.hsqldb.util.DatabaseManager) for instance copies the entire cell value or row value no matter how large (or was that the entire result set?) 2. Seems like WebLogic's problem as long as Netbeans doesn't crash. 3. I can't say I agree here, since we're only talking about copying a single row or a cell value. They are not likely to be larger than half the available memory on the computer. My personal opinion is that any users that try to copy 500MB cell values to the clipboard can blame themselves. Most likely, they are already blamed by the DBA :-) Anyway, you're the one making the decision. Saving the result set as a CSV-file (or "selectable separator"-file) would still a very nice new feature, since these are easy to import into spreadsheets and other tabular data programs. I think nobody would mind if this means re-running the query.
Will try to implement in a future version.
Fixed.
Verified with build 080714.