For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 2 replies, 2 voices, and was last updated 19 years ago by
.
-
Posts
-
– System Setup ——————————-
Operating System and version: Linux 2.6.9-11.ELsmp #1 SMP Fri May 20 18:26:27 EDT 2005 i686 i686 i386 GNU/Linux
Eclipse version: 3.2
Eclipse build id:
Fresh Eclipse install (y/n):
If not, was it upgraded to its current version using the update manager?
Other installed external plugins:
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*:
MyEclipse version: 5.5M1
Eclipse JDK version:
Application Server JDK version:
Are there any exceptions in the Eclipse log file?If this is a DB related question please answer the following:
RDBMS vendor and version: several
JDBC driver vendor and version, and access type (thin, type-2, etc):
Connection URL:
Eclipse error logs related to com.genuitec.eclipse.sqlexplorer packages:– Message Body ——————————-
Frequently I want the DB explorer to have an SQL editor. I use this as a work area and don’t want to save it although I may want to keep the commands around for my edit session.If I refactor in the Java area, the SQL editor is considered “unsaved” and must be saved or deleted for the refactor to occur. The SQL editor does not participate in refactoring and should not be tested.
I believe this may be a side effect of the save requiring all “editors” to be in a clean state, and the SQL editor is a type of editor. I’ll make a note of this issue to see if we can get the refactor cycle to ignore the unsaved SQL editor.
