How do you access two databases in Grails

Question

Grails makes it very easy to configure datasources for different environments (development, test, production) in its DataSources.groovy file, but there seems to be no facility for configuring multiple datasources in one environment. What to I do if I need to access several databases from the same Grails application?

Answer 1

Connecting different databases in different domain classes is very easy in Grails 2.x.x.

for example

development {
    dataSource {//DEFAULT data source
      .
      .
    }
dataSource_admin { //Convention is dataSource_name
        url = "//db url"
        driverClassName = "oracle.jdbc.driver.OracleDriver" 
        username = "test"
        password = 'test123'
    }
dataSource_users {

    }
}

You can use any datasources in your domain classes by

class Role{
   static mapping = {
      datasource 'users'
   }
}

 class Product{
    static mapping = {
      datasource 'admin'
   }
 }

For more details look at this

Answer 2

If using Grails 2.0 or higher, there is no need for the plugin, it is supported natively.

http://www.grails.org/doc/latest/guide/single.html#multipleDatasources

Answer 3

There is now Grails plugin that enables the use of multiple datasources directly with Grails' GORM layer: http://burtbeckwith.com/blog/?p=70

Answer 4

Grails 2.0 can handle multiple data sources without a plugin:

Example with a different datasource for the dev(h2 dataSource) and test(mysql dataSource_mysql) environments:

DataSource.groovy:

dataSource {
    pooled = true
    driverClassName = "org.h2.Driver"
    username = "sa"
    password = ""
}
dataSource_mysql {
    dialect = org.hibernate.dialect.MySQLInnoDBDialect
    driverClassName = 'com.mysql.jdbc.Driver'
    username = "user"
    password = "pass"
    url = "jdbc:mysql://mysqldb.com/DBNAME"
}
hibernate {
    cache.use_second_level_cache = true
    cache.use_query_cache = false
    cache.region.factory_class = 'net.sf.ehcache.hibernate.EhCacheRegionFactory'
}

// environment specific settings
environments {
    development {
        dataSource {
            configClass = HibernateFilterDomainConfiguration.class
            dbCreate = "update" // one of 'create', 'create-drop', 'update', 'validate', ''
            url = "jdbc:h2:file:../devDb;MVCC=TRUE"
            sqlLogging = true
        }
    }
    test {
        dataSource_mysql {
            configClass = HibernateFilterDomainConfiguration.class
            dbCreate = "create" // one of 'create', 'create-drop', 'update', 'validate', ''
            sqlLogging = true
        }
    }
    production {
        dataSource {
            dbCreate = "update"
            url = "jdbc:h2:prodDb;MVCC=TRUE;LOCK_TIMEOUT=10000"
            pooled = true
            properties {
               maxActive = -1
               minEvictableIdleTimeMillis=1800000
               timeBetweenEvictionRunsMillis=1800000
               numTestsPerEvictionRun=3
               testOnBorrow=true
               testWhileIdle=true
               testOnReturn=true
               validationQuery="SELECT 1"
            }
        }
    }
}

Answer 5

Do you really want to do this? In my experience, the usual scenario here is:

1. An application manages its own data in its own database schema
2. Often, the application will require data from other sources (for example, so reference data doesn't get copied and pasted)

I've normally always had the luxury of all the schemas residing on the one database instance. Therefore, my application:

• only has one database connection - which is to the schema it owns and has read/write access
• the other applications 'export' their data via views
• my application has read access to those views, and has a synonym for that view making it appear local

The reason behind using views is so that the application that is exposing the data

1. knows explicitly that it is being exported and what is being exported
2. does not expose the internal structure of the schema (so if the internal structure changes, as long as the view is correct the consuming apps don't know)

I haven't actually had to do this with a Grails application, but the approach should work.

Another approach to sharing data across applications is to create a web service to expose the data. Grails makes this easy.

Hope that helps, but this approach may not be applicable for all situations.

Answer 6

The following post seems to be the best source of information on the subject:

How to get mutli-dataSource in grails

It boils down to:

• Define datasource1 in DevelopmentDataSource
• Define datasource2 in resources.xml
• Write a DAO for CRUD of the domain objects using datasource2
• In hibernate.cfg.xml, list all domain objects.

Only the first datasource will have dynamic finder methods.

If its a really simple query you are after and don't mind not having the ORM features you could use Groovy SQL or the native SQL features of Hibernate.