New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow database configuration for the console #76

Closed
ypujante opened this Issue Jul 19, 2011 · 2 comments

Comments

Projects
None yet
2 participants
@ypujante
Member

ypujante commented Jul 19, 2011

Currently changing the database used under the cover is not exposed as a configuration parameter. Need to make it configurable (and also update the documentation explaining the steps to use a different database). Make sure it works with MySql.

@li-mdubey

This comment has been minimized.

Contributor

li-mdubey commented Jul 19, 2011

We already do this. Instead of having following line in the console config file:

//hsqldb
console.db.url='jdbc:hsqldb:file:/tmp/consoledb/prodDb;shutdown=true'

You can do this:

//sqlite support
dataSource.url='jdbc:sqlite:/usr/local/apache-tomcat-6.0.29/my.sqlite'
dataSource.driverClassName='org.sqlite.JDBC'
dataSource.logSql=true
dataSource.dialect='dialect.SQLiteDialect'
dataSource.dbCreate='update'

Also for any new database, you only need to make sure that the right driver is packaged with console.war.

@ypujante

This comment has been minimized.

Member

ypujante commented Jul 19, 2011

I need to give explanation on how to do that without tweaking the war file (there should be a way to drop the driver in the container classpath... which is what I need to test and document)

@ghost ghost assigned ypujante Sep 13, 2011

ypujante added a commit that referenced this issue Sep 16, 2011

#76: documentation for using MySql with glu
 - only documentation change as grails already support 'any' database

@ypujante ypujante closed this Sep 16, 2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment