Your experience is almost the same as mine... I was really thrown by the docs and it took me a couple of days of trial and error before I got a MySql connection, then had no prob setting up an ODBC connection. I found that there was no way to get ProjectViewer to work with JEdit 4.1 stable and needed to upgrade (to JEdit 4.2pre14). I'm always nervous about using non-stable releases.

My own problem now is that the projects keep losing their settings, or SQL forgets about them, or something. Sometimes I only need to open the project properties and click Apply, other times I have to completely reconfigure the project. Usually I only need to do this once per JEdit session, but sometimes I need to do this whenever I switch databases.

By the way, the only way I can find to switch databases is through ProjectViewer. The SQL drop down seems to have no function whatsoever.

The SQL plugin would be really handy to produce certain reports I need on a daily basis, but would only be worthwhile if I could write a macro or something automated. As things stand so far I'm as well off writing a Perl script or Java utility instead. Too bad.

Hi there,

I've got the SQL plugin (0.97) working in JEdit 4.1 final.(Oracle 9i & ODBC/access) I tried the latest release but the system freezed... bit to early to use the beta I think.

I'm getting these entries in the activity log:

[debug] SqlPlugin: Looking for the property [sql.currentServerName] of null
[debug] SqlPlugin: Error!

The activity log vaildates that the JDBC drivers are getting loaded and the database server is up and running, but when I use "Choose the server", the combo box is empty.

Is there something else that I need to configure to get the plugin working?

Thanks,
Mark L

Windows	XP Pro
Java	1.5-beta
jEdit	4.2pre12
SQL	0.98
Common Controls	0.82
Project Viewer	2.0.2
XML	0.13

I got the SQL plugin working today. I have been stalling this, since I have about 6 other querying tools to use. Now that it's working, I find querying databases very convenient from jEdit. Since the plugin doesn't maintain an active connection, it's easy to change the server and reexeute statements, barring any syntax modifications.

SQL plugin does not see the jdbc jar files that I copy to the JDK_HOME/jre/lib/ext directory automatically, as I would expect it to, so I have to to point to them explicitly through the SQL plugin option. No big deal.

I then copied the SQL Server XML config file and only changed the serverType name property and verified that it appeared in the 'SQL server type' drop down list(Exit and restart jEdit). After that I changed one attribute at a time until I got it the way I wanted. I noticed that any incorrect modifications to the config file resulted in the new serverType not showing and sometimes all the existing serverTypes would disappear as well.

I created one project that contains all my connection definitions. The server dropdown list contains all the servers for the active project. Putting each connection into a seperate project will make switching databases difficult.

Hope this helps,
Mark