[Helma-user] New Helma User - database configuration problems

[Kevin Monceaux]

Robert,

On Wed, Aug 23, 2006 at 08:13:51PM +0200, Robert Gaggl wrote:
  
> i don't know what version of mysql-server resp. mysql-jdbcdriver you're 
> using, but in all of my db.properties (and in the tutorial) the line 
> specifying the driver looks like this:
> 
> myDataSource.driver   = org.gjt.mm.mysql.Driver

I'm guessing that's in there for backwards compatability.  Looking in the
mysql JDBC driver's jar file it contains both:

com/mysql/jdbc/Driver.class

and

org/gjt/mm/mysql/Driver.class

One can use either org.gjt.mm.mysql.Driver or com.mysql.jdbc.Driver.  The
documentation on the MySQL site suggests the latter.

> did you look in helma's logfiles for any complaints? of course, if you 
> have logDir set to "console", you should see it there...

The term doh comes to mind.  Apparently I hadn't had nearly enough caffeine
this morning when I was trying out Helma.  I didn't even think to look for
log files.  Most of the "built-in" test servers that come with the various
frameworks I've been playing with recently, such as Catalyst, Ruby on Rails,
etc., display error messages on the console.  The Helma logs confirmed what
I suspected.  It was a class path problem.  I had tried both MySQL and
PostgreSQL.  I tried adding the path to the driver file to my CLASSPATH
variable and tried putting the driver jar file in Helma's lib directory.
Putting the driver jar files in Helma's lib/ext directory did the trick.  My
test MySQL server doesn't appear to be set up properly to play nicely with
JDBC.  After getting the driver jar files in the right spot I got a
connection refused from MySQL.  But, that's okay.  I prefer PostgreSQL
anyway.  I'm now progressing through the tutorial using PostgreSQL as my
database.


Kevin
http://www.RawFedDogs.net
http://www.WacoAgilityGroup.org
Bruceville, TX

Si hoc legere scis nimium eruditionis habes.