On 8/9/2011 3:46 PM, Casper Bang wrote:
Now with 1.7 it's once again unusable - remarkably, incremental
loading of rows when visualizing table data is all screwed up. So I
have to keep JDK 1.6 only to run SQLDeveloper. It's irritating
because that's a program from the same company that now provides JDK,
so it looks like an ugly case of left hand not knowing what the right
hand does. It's not a recent bug from the very latest JDK 7 builds; I
noticed the problem months ago, so they just didn't test during the
beta period, or didn't care.
It's interesting that SQLDeveloper always does version checking and
warns users of potential problems, it kind of says something about the
developers lack of trust in binary backwards compatibility of the Java
platform. However, what REALLY bothers me about SQLDeveloper, is how
it always freezes when you loose a connection over VPN, or just keep
it open for more than an hour or so.
Or that if you click on the wrong thing (the dreaded "Data" tab), you'll
get an OutOfMemoryError as it tries to bring the entirety of the data
table into memory -- without regard for how big the table is or how
little memory you have...
--
Jess Holle
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
