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.
Created attachment 122322 [details] text in varchar(max) columns is not displayed correctly. 1. Connect to a SQL Server database (I don't know if this is a problem on other DBs). 2! Display a resultset from a table that includes varchar(max) columns. The column text is not shown correctly. It looks like NB is detecting the varchar(max) columns as LONGVARCHAR columns. I'm not sure if that's correct.
NB version/build number ? JDK version ? .... and please reopen once you provide pending data, thanks in advance.
*** This bug has been marked as a duplicate of bug 215973 ***
The bug spans every operating system, every compatible JDK, and multiple builds (including 7.2). Latest build w/ JDK6u33 on OSX: Product Version: NetBeans IDE Dev (Build 201207270002) Java: 1.6.0_33; Java HotSpot(TM) 64-Bit Server VM 20.8-b03-424 System: Mac OS X version 10.8 running on x86_64; MacRoman; en_US (nb) User directory: /Users/alvin/Library/Application Support/NetBeans/dev Cache directory: /Users/alvin/Library/Caches/NetBeans/dev Netbeans 7.2 w/ (blurry) JDK7u5 on OSX: Product Version: NetBeans IDE 7.2 (Build 201207171143) Java: 1.7.0_05; Java HotSpot(TM) 64-Bit Server VM 23.1-b03 System: Mac OS X version 10.8 running on x86_64; US-ASCII; en_US (nb) User directory: /Users/alvin/Library/Application Support/NetBeans/7.2 Cache directory: /Users/alvin/Library/Caches/NetBeans/7.2 6/13 build w/ JDK6u24 on Windows: Product Version: NetBeans IDE Dev (Build 201206130001) Updates: Updates available Java: 1.6.0_24; Java HotSpot(TM) 64-Bit Server VM 19.1-b02 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb) User directory: C:\Users\athompson\AppData\Roaming\NetBeans\dev Cache directory: C:\Users\athompson\AppData\Local\NetBeans\Cache\dev
Your result, that this happens every where, is correct - it's actually intended (see comment #1 on bug #215973). Please don't reopen this bug, as it is a duplicate of bug #215973 and it's not helping to have this issue reported twice. Please add additional information at the mentioned bug. Thanks! *** This bug has been marked as a duplicate of bug 215973 ***
Sorry, I was following your instructions in comment #1. :P