That fixed it. A grep/search on the Java tree didn't show this
connection URL anywhere and it never occurred to me that the URL would
be embedded in the SQL script itself.
I appreciate your help.
Should I submit this to Jira as a bug, or did you already do that?
Rajesh Kartha wrote:
A. Rick Anderson wrote:
Is there a bug in the eclipse plug-in for ij? I've installed the
eclipse-plug-in and when attempting to run the labs, it fails with the
following message. I have installed the Derby Nature in the project
DerbyLab.
ij> connect
'jdbc:derby:net://localhost:1527/jayDB;create=true;user=APP;password=APP;';
ERROR 08001: No suitable driver found for
jdbc:derby:net://localhost:1527/jayDB;create=true;user=APP;password=APP;
When I googled this error message, it showed that the URL is different
then derby is expecting it to be, but this would imply that there is a
bug in the ij.bat script, something that would never pass any form of
regression test.
I've tried setting DERBY_HOME, and that didn't change the behavior.
When I did the derby getting_started activities from the command-line,
they all worked fine. It's just within Eclipse that I seem to be
having this challenge.
The only JRE or JDK on my machine is 1.6. But I have Java 1.6, derby
10.2.2 and I downloaded the latest JavaDB from Sun. But since they
all fundamentally share the exact same code, I don't see where this
should cause a problem.
Hi Rick,
http://db.apache.org/derby/integrate/plugin_slides.html
Looks like the url in the jay_tables.sql file needs a minor fix and change
connect
'jdbc:derby:net://localhost:1527/jayDB;create=true;user=APP;password=APP;';
to
connect
'jdbc:derby://localhost:1527/jayDB;create=true;user=APP;password=APP;';
The other sql files show the correct url. The above url uses the Derby
client driver to connect
to the server.
--
A. Rick Anderson
