grailsmysql_grails连接mysql

Grails切换到

mysql

数据库需要做如下的配置&＃xff1a;

1、将my

sql-connector-java-5.1.22-bin.jar驱动复制到Grails应用的根目录lib下面。

2、修改conf/DataSource.groovy;Grails默认用的是H2

数据库&＃xff0c;我们需要将driverClassName &＃61; "org.h2.Driver" 改成 driverClassName &＃61; &＃39;

com.mysql.jdbc.Driver&＃39;&＃xff1b;url改成我们自己数据库的url

上面的改法会发生几个问题&＃xff0c;

1、如果单纯光把驱动复制到lib目录&＃xff0c;会发生异常&＃xff1a;

java.lang.ClassNotFoundException: com/mysql/jdbc/Driver

找不到这个驱动&＃xff0c;此时我们还需要在BuildConfig.groovy文件中加入下面的配置&＃xff1a;

dependencies {

runtime &＃39;mysql:mysql-connector-java:5.1.22&＃39;

}

2、尽管我们自己的应用用的是mysql&＃xff0c;但是可能某些插件或者框架用的是H2数据库&＃xff0c;这样如果我们之配置mysql的数据源&＃xff0c;可能导致数据库连接驱动不匹配的异常。

因此我们需要保留原来的数据源配置&＃xff0c;另外添加mysql的数据源。

dataSource {

pooled &＃61; true

driverClassName &＃61; "org.h2.Driver"

username &＃61; "sa"

password &＃61; ""

}

hibernate {

cache.use_second_level_cache &＃61; true

cache.use_query_cache &＃61; false

cache.region.factory_class &＃61; &＃39;

net.sf.ehcache.hibernate.EhCacheRegionFactory&＃39;

}

// environment specific settings

environments {

development {

dataSource {

dbCreate &＃61; "create-drop" // one of &＃39;create&＃39;, &＃39;create-drop&＃39;, &＃39;update&＃39;, &＃39;validate&＃39;, &＃39;&＃39;

url &＃61; "jdbc:h2:mem:devDb;M

VCC&＃61;TRUE;LOCK_TIMEOUT&＃61;10000"

}

dataSource_mysql {

dialect &＃61; org.hibernate.dialect.MySQLInnoDBDialect

driverClassName &＃61; &＃39;com.mysql.jdbc.Driver&＃39;

username &＃61; &＃39;root&＃39;

password &＃61; &＃39;root&＃39;

url &＃61; &＃39;jdbc:mysql://localhost/DojoGrails&＃39;

dbCreate &＃61; &＃39;update&＃39;

}

}

test {

dataSource {

dbCreate &＃61; "update"

url &＃61; "jdbc:h2:mem:testDb;

MVCC&＃61;TRUE;LOCK_TIMEOUT&＃61;10000"

}

}

production {

dataSource {

dbCreate &＃61; "update"

url &＃61; "jdbc:h2:prodDb;MVCC&＃61;TRUE;LOCK_TIMEOUT&＃61;10000"

pooled &＃61; true

properties {

maxActive &＃61; -1

minEvictableIdleTimeMillis&＃61;1800000

timeBetweenEvictionRunsMillis&＃61;1800000

numTestsPerEvictionRun&＃61;3

testOnBorrow&＃61;true

testWhileIdle&＃61;true

testOnReturn&＃61;true

validationQuery&＃61;"SELECT 1"

}

}

}

}

上面是DataSource配置的例子&＃xff0c;添加了第二个数据源 dataSource_mysql

在这个多数据源应用里&＃xff0c;我们需要在使用dataSource_mysql数据源的domain类里加入如下配置:

static map

ping &＃61; {

datasource &＃39;mysql&＃39;

}

以表明这个domain用的是哪个数据源&＃xff1b;

&＃xff5e;&＃xff5e;&＃xff5e;&＃xff5e;&＃xff5e;&＃xff5e;&＃xff5e;&＃xff5e;&＃xff5e;&＃xff5e;&＃xff5e;&＃xff5e;&＃xff5e;&＃xff5e;

官方对多数据源的说明&＃xff1a;

Configuring Additional DataSources

The default DataSource configuration in grails-app/conf/DataSource.groovy looks something like this:

dataSource {

pooled &＃61; true

driverClassName &＃61; "org.h2.Driver"

username &＃61; "sa"

password &＃61; ""

}

hibernate {

cache.use_second_level_cache &＃61; true

cache.use_query_cache &＃61; true

cache.provider_class &＃61; &＃39;net.sf.ehcache.hibernate.EhCacheProvider&＃39;

}

environments {

development {

dataSource {

dbCreate &＃61; "create-drop"

url &＃61; "jdbc:h2:mem:devDb"

}

}

test {

dataSource {

dbCreate &＃61; "update"

url &＃61; "jdbc:h2:mem:testDb"

}

}

production {

dataSource {

dbCreate &＃61; "update"

url &＃61; "jdbc:h2:prodDb"

}

}

}

This configures a single DataSource with the Spring bean named dataSource. To configure extra DataSources, add another dataSource block (at the top level, in an environment block, or both, just like the standard DataSource definition) with a custom name, separated by an underscore. For example, this configuration adds a second DataSource, using MySQL in the development environment and

Oracle in production: environments {     development {         dataSource {             dbCreate &＃61; "create-drop"             url &＃61; "jdbc:h2:mem:devDb"         }         dataSource_lookup {             dialect &＃61; org.hibernate.dialect.MySQLInnoDBDialect             driverClassName &＃61; &＃39;com.mysql.jdbc.Driver&＃39;             username &＃61; &＃39;lookup&＃39;             password &＃61; &＃39;secret&＃39;             url &＃61; &＃39;jdbc:mysql://localhost/lookup&＃39;             dbCreate &＃61; &＃39;update&＃39;         }     }     test {         dataSource {             dbCreate &＃61; "update"             url &＃61; "jdbc:h2:mem:testDb"         }     }     production {         dataSource {             dbCreate &＃61; "update"             url &＃61; "jdbc:h2:prodDb"         }         dataSource_lookup {             dialect &＃61; org.hibernate.dialect.Oracle10gDialect             driverClassName &＃61; &＃39;oracle.jdbc.driver.OracleDriver&＃39;             username &＃61; &＃39;lookup&＃39;             password &＃61; &＃39;secret&＃39;             url &＃61; &＃39;jdbc:oracle:thin:&＃64;localhost:1521:lookup&＃39;             dbCreate &＃61; &＃39;update&＃39;         }     } } You can use the same or different databases as long as they&＃39;re supported by Hibernate. Configuring Domain Classes If a domain class has no DataSource configuration, it defaults to the standard &＃39;dataSource&＃39;. Set the datasource property in the mapping block to configure a non-default DataSource. For example, if you want to use the ZipCode domain to use the &＃39;lookup&＃39; DataSource, configure it like this; class ZipCode {    String code    static mapping &＃61; {       datasource &＃39;lookup&＃39;    } } A domain class can also use two or more DataSources. Use the datasources property with a list of names to configure more than one, for example: class ZipCode {    String code    static mapping &＃61; {       datasources([&＃39;lookup&＃39;, &＃39;auditing&＃39;])    } } If a domain class uses the default DataSource and one or more others, use the special name &＃39;DEFAULT&＃39; to indicate the default DataSource: class ZipCode {    String code    static mapping &＃61; {       datasources([&＃39;lookup&＃39;, &＃39;DEFAULT&＃39;])    } } If a domain class uses all configured DataSources use the special value &＃39;ALL&＃39;: class ZipCode {    String code    static mapping &＃61; {       datasource &＃39;ALL&＃39;    } }