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 # : 200809020201 ] [ JDK VERSION : 1.6.0_06 ] When doing a query, string fields are displayed so narrow they are unreadable. User has to go to each one in turn and expand the column to see anything (see attached screenshot).
Created attachment 68875 [details] screenshot
Which database are you using, also can send me the create table script as well as some data, so that I can try that out locally?
Created attachment 69079 [details] DDL to create database
Created attachment 69080 [details] Postgres dump of database
1) psql template1 2) create database phoenix owner weyco; 3) \i phoenix.i 4) (from command line) pg_restore -d phoenix phoenix-145929.tar
I would like to kindly ask you to reconsider the decision not to fix this issue for 6.5: - it was filed by a NetCAT participant. These are volunteers which dedicate a lot of their time to improve NetBeans, and their feedback should not be taken lightly. - the reporter has given a lot of detail trying to help you reproduce the issue. If you have reproduced the problem using the reporter's script, but determined that the issue is hard to fix, it would be nice to document your findings here, so that the community knows that he issue is being addressed property, but it is not fixable for 6.5. Thanks.
OK, I will give it a try.
jawed, can You take a look at this issue? This issue is P3, but it is reported by NetCAT participant and therefore this issue is going to be included into NetBeans 6.5 Patch 1. Please fix it till 27 November (this is code freeze date for Patch 1) or update this issue with justification why the fix isn't possible till this date. Thanks.
The issue didn't pass the nomination process by nomination cut-off date. It has been marked as 65fixes2-candidate.
*** Issue 150275 has been marked as a duplicate of this issue. ***
Needs Verification http://hg.netbeans.org/main/rev/a17b8f8cf78c
Verified with build 081204.
sivashankari, have you provided the correct changeset? There is following commit message "Issue # 154170 Error message should appear instead of Information" in the changeset a17b8f8cf78c which you provided. But this issue has #145929 and the subject is "[65cat] string fields squished in database explorer". Unfortunately, I haven't found any commit message containing "145929" in the main repository. Could you please confirm that the changeset 17b8f8cf78c is the correct one?
Actually I tried to reproduce this issue with my steps, which are described in duplicate issue #150275 and wasn't able to reproduce. Probably we should ask also reporter if this fix is OK. gholmer, can You verify that this issue was really fixed? But anyway, sivashankari, can you provide the correct changeset? Or we should test this issue one more time?
It is the correct changeset which includes several other fixes apart from the CR mentioned.
Can I just grab a nightly to test this (http://bits.netbeans.org/download/trunk/nightly/latest/)?
> changeset which includes several other fixes apart from the CR mentioned. In this case all several issues except duplicates should be marked as patch candidates.
gholmer, yes You can.
Yes, that fixes it. The fields are no longer squished, thanks very much.
Please, provide a changeset with changes related to this issue only. As was mentioned, the provided changeset a17b8f8cf78c includes several other fixes apart from the CR mentioned so it cannot be integrated into the high resistance release65_fixes branch.
Sivashankari, are you able to provide the changeset with changes related to this issue only? We really need it. But it seems to me that this issue should be excluded from Patch 2 since we can't port available changeset. Petr, by the way, can we port this changeset if I mark the rest of the issues, which were fixed with this changeset, as candidates for Patch 2? Or it will be redundant work? If we can, then Sivashankari, please provide all issues, which were fixed with the changeset a17b8f8cf78c, tomorrow COB.
I prefer the option with the exact changeset but marking issues, which were fixed by mentioned changeset could work as well. OTOH added issues could lead to huge number of additional changes. In that case, it isn't acceptable.
No solution for the release65_fixes branch was provided by 65patch2 code freeze. The issues has been moved to 65patch3.
This is disappointing. It is time-consuming to have to resize every column every time this happens in order to view the data.
gholmer, don't worry. We just don't have enough time to port necessary fix, but we definitely will work on this issue for Patch 3.
The status whiteboard "65fixes4-candidate" has been removed. At this time our proactive patches for the NetBeans 6.5.x IDE have concluded. If you own a Sun service plan contract for NetBeans, you may wish to contact Sun Service http://www.sun.com/contact/support.jsp to request a fix via the product defect escalation process. For more information on purchasing a Sun service plan contract for NetBeans, refer to the service plan item "Sun Software Service Plans (S3P) for Developers" in the Sun Service table found on our NetBeans Support Resources page http://www.netbeans.org/kb/support.html