I feel like all the eclipse sql plugins are missing the absolute most important feature: hooking into an existing jdbc session.
This is incredibly useful during debugging unit/integration tests for example: You can see what would be in the DB even though the currently running transaction is not committed yet.
For me it's not such a high priority anymore since I found a way to "hack" Squirrel SQL to be able and do just that. It was not even that hard to do, which is why I am really wondering why not all the Eclipse plugins actually provide this feature.
From my squirrel hack... Prerequisites:
- project to be debugged needs to have the hacked squirrel-sql in the classpath (possible improvement: somehow inject the hacked squirrel at runtime into the classpath)
- user right clicks on a stack element which has a jdbc session somewhere referenced which can be resolved through reflection
import org.eclipse.core.internal.jobs.JobStatus;
import org.eclipse.core.runtime.IProgressMonitor;
import org.eclipse.core.runtime.IStatus;
import org.eclipse.core.runtime.jobs.Job;
import org.eclipse.debug.core.model.IDebugElement;
import org.eclipse.debug.core.model.IWatchExpression;
import org.eclipse.debug.internal.core.WatchExpression;
class SquirrelStarterJob extends Job {
}