Replacing GenericUserDAO

[Migrated From Jforum.net]

Greetings,

I'm trying to override GenericUserDAO for a MySQL database.

I created a subclass of GenericUserDAO named QRUserDAO and overrode the factory method MysqlDataAccessDriver.newUserDAO() by creating a subclass named QRDataAccessDriver.

I edited the conf/database/mysql/mysql.properties file so that it would load QRDataAccessDriver instead of MysqlDataAccessDriver.

However, my changes don't create a QRDataAccessDriver object. It turned out that there's another dao.driver=net.jforum.dao.mysql.MysqlDataAccessDriver property in jforum-custom.conf that is overriding the one in myqel.properties. If I remove it, I get the message

16:09:01,666  INFO [ConfigLoader        ] Loading JDBC driver com.qr.jforum.dao.QRDataAccessDriver
...
16:09:01,907 DEBUG [DatabaseWorkarounder] MySQL Version: 4.0.24
16:09:01,908  INFO [DatabaseWorkarounder] MySQL DAO class is incorrect. Setting it to net.jforum.dao.mysql.MysqlDataAccessDriver
16:09:01,919  INFO [ConfigLoader        ] Loading JDBC driver net.jforum.dao.mysql.MysqlDataAccessDriver

Looking in DatabaseWorkarounder it appears that net.jforum.dao.mysql.MysqlDataAccessDriver is hard-coded. If the class of the driver is anything other than MysqlDataAccessDriver, the driver is replaced and the configuration overridden.

So how does one replacing GenericUserDAO?

[originally posted on jforum.net by jbucanek]

[Migrated From Jforum.net]

hhhm.. I ignored this possibility.

This "workarounder" exists because the shit MySQL AB does on every new version of their database server..

You can register this bug at Jira, and, to make it working for you now, you can just change the code to not use the JForum version of the mysql dao driver.

Rafael
[originally posted on jforum.net by Rafael Steil]

[Migrated From Jforum.net]

For now, that's what I did.

	private void handleMySql40x() throws Exception
	{
		// (jlb 15-Feb-2007) Ignore this test until we can figure out a clean way of
		//	overriding MysqlDataAccessDriver with QRDataAccessDriver
		//this.ensureDaoClassIsCorrect(MYSQL_DATA_ACCESS_DRIVER);

Since my installation of MySQL won't be changing any time soon, this will work for now.

I'll file a bug.

Thinking about the problem, there should be a better way to handle this, but I'll have to put on my thinking cap.
[originally posted on jforum.net by jbucanek]