Article View: borland.public.jbuilder.database
Article #282Re: MySQLException: No suitable driver.
From: Zachary
Date: Sat, 28 Jan 2006 04:25
Date: Sat, 28 Jan 2006 04:25
20 lines
3005 bytes
3005 bytes
Mr. Furbacher, . Terribly sorry for the gaffes. Let me see... . You have guessed correctly that the Subject contains the exception with which I'm struggling... "MySQLException: No suitable driver. . In this case, 'macroprogram' and 'microprogram' are programs in relation to one another. The macroprogram contains all elements of the fully functional microprogram, and does other stuff. Unfortunately, in this case the big one does everything it's supposed to /except/ connect to the database. . I hadn't thought about the e-mail newsgroup users when referring to Luca's message (which appears below new ones on the web version). Bad news, I made a bad comparison. Good news, I was right about starting a new thread because it wasn't related. . I agree completely with your analysis of flailing. I've tried dozens of different suggestions, one of which included editing the config file to include the appropriate jar. You'll note that after reading the contents of said config file I didn't edit it, as it was supposed to include all the jars in a particular folder. I put the "mysql-connector*.jar" into the appropriate folder. Still no success. . Ah, get it about the environment-inside-an-environment explanation... and now I get it about why it didn't read it... lacking brain cells. . Under "Project Properties", in the "Required Libraries" tab, I have definitely added the mysql-connector. Oddly, I didn't do any such thing for the smaller program. . Okay, after removing it and re-adding it, I'm getting a completely different error: "SQLException: Communication link failure: java.io.IOException, underlying cause: Unexpected end of input stream ** BEGIN NESTED EXCEPTION ** ... (plus more than you probably care to read) ... . After going through and plucking out and throwing away all the loads of places I've copied mysql-connector, I've done the following: - Downloaded the latest connector from MySQL-AB - Created a new library with said connector as suggested in the Help file. - Required said library within "Project Properties" Aaaand... we're back to "No Suitable Driver". I'm going to bed.
Technical Details
Message-ID:
<43db0038$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!proxad.net!212.101.4.254.MISMATCH!solnet.ch!solnet.ch!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<43d9168d$1@newsgroups.borland.com> <43d936e3$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 1073da,b0ce4766862eec7f X-Google-Attributes: gid1073da,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Zachary" <zanders@emory.edu> Sender: "Zachary" <zanders@emory.edu> Reply-To: "Zachary" <zanders@emory.edu> Subject: Re: MySQLException: No suitable driver. Newsgroups: borland.public.jbuilder.database X-User-Info: 170.140.166.65 References: <43d9168d$1@newsgroups.borland.com> <43d936e3$1@newsgroups.borland.com> NNTP-Posting-Host: 207.105.83.66 Message-ID: <43db0038$1@newsgroups.borland.com> Date: 27 Jan 2006 21:25:12 -0700 X-Trace: newsgroups.borland.com 1138425912 207.105.83.66 (27 Jan 2006 21:25:12 -0700) Lines: 20 Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!proxad.net!212.101.4.254.MISMATCH!solnet.ch!solnet.ch!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail