Where answers come from

Some pages can ask a language model questions. Set this up once; your choice is remembered in this browser for the whole site.

Model source
Use another source instead

Smallest-to-largest weight downloads. Qwen3.5 0.8B is our starting choice for page Q&A. GPU estimates are not total RAM: leave room for the browser, context and temporary buffers. Hardware changes speed and capacity; answers still need checking.

Session-only loading avoids saving model weights, uses extra RAM and downloads again after unloading. Turn it off to save downloads. Delete-data-on-exit or private browsing may impose a much smaller storage limit than the displayed estimate.

You sign in on OpenRouter; it gives this page a key for your account.

A free account does not make every model free. Choose a model with a listed :free variant; merely adding that suffix does not create one. Check free-model availability and pricing.

Chat

AI assistant, not Shawn Hartsock. It does not speak for him.

Inspect the page excerpt

Up to 4,800 characters, not the whole site. Recent conversation turns are retained within the model’s context limit.

Ask about this page, or just say hello.

Ready when you are.

Not saved or uploaded automatically. Closing keeps this conversation in this tab; changing pages starts a new one. Model replies can be wrong.

Grails Datasource, legacy database, and you

Originally published .

Any one out there trying to work with Groovy, Grails, and legacy databases?

Well, I am and I thought I’d share with you my final dataSource configuration. I’m using a legacy database that drove an Apache + mod_perl web site that had a MySQL 3.x database. The Groovy/Grails project I’m working on will interact with that data (right now as a read-only service) and here’s the final dataSource definition I ended up using for our first beta.


import org.codehaus.groovy.grails.orm.hibernate.cfg.GrailsAnnotationConfiguration

/**

 * This project is driven off of Legacy data.

 * Use update to prevent wiping old tables...

 * much of the data is accessed using JPA classes generated by

 * the Hibernate3 reverse engineer tool.

 ********************************************************************/

 dataSource {

  configClass = GrailsAnnotationConfiguration.class

  dbCreate = "update"

  dialect= org.hibernate.dialect.MySQLMyISAMDialect // or perhaps MySQL5Dialect

  pooled = false

 }

 environments {

  development {

   dataSource {

    driverClassName = "com.mysql.jdbc.Driver"

    url = "jdbc:mysql://localhost:3306/legacy?zeroDateTimeBehavior=convertToNull"

    username = "legacy"

    password = "legacy"

   }

  }

  test {

   dataSource {

    driverClassName = "com.mysql.jdbc.Driver"

    url = "jdbc:mysql://localhost:3306/legacy?zeroDateTimeBehavior=convertToNull"

    username = "legacy"

    password = "legacy"

   }

  }

  production {

   dataSource {

    jndiName = "java:/LegacyDS"

   }

  }

}

The LAMP stack was upgraded to use MySQL 5 recently so we can set up our new projects using the setting dialect= org.hibernate.dialect.MySQLInnoDBDialect which will give us the ability to use actual foreign key relationships. That’s a big deal if you are a LAMP developer. I suppose that in short order I will be a Grails, Linux, Apache, MySQL developer… a GLAM developer… ah… no… lets not call it that.

BTW: I deploy to a JBoss Application server in production which manages the DataSources in a legacy-ds.xml file under /usr/local/jboss/server/default/deploy that’s why my production dataSource uses the jndi lookup.

Explore the map · Browse by topic and date