Comments on: No Dialect mapping for JDBC type: -1 http://www.javathinking.com/2008/04/no-dialect-mapping-for-jdbc-type-1/ Java and software development related thoughts Thu, 29 Dec 2011 20:59:47 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: David http://www.javathinking.com/2008/04/no-dialect-mapping-for-jdbc-type-1/comment-page-1/#comment-528 David Tue, 16 Dec 2008 11:50:22 +0000 http://www.javathinking.com/?p=85#comment-528 Upgrade your MySQL version to 5.0.3 and change TEXT type to VARCHAR(N) N>[0-65535]. Upgrade your MySQL version to 5.0.3 and change TEXT type to VARCHAR(N) N>[0-65535].

]]> By: paul http://www.javathinking.com/2008/04/no-dialect-mapping-for-jdbc-type-1/comment-page-1/#comment-368 paul Tue, 22 Apr 2008 22:24:54 +0000 http://www.javathinking.com/?p=85#comment-368 Thanks Burt, I meant to add a note saying that I do have other tables with TEXT columns and they work fine when using straight GORM or criteria. So how do you use addScalar from your domain class? Can you simply use the mapping property? static mapping = { columns { postCode type:'text' } } Note, I'm working with Grails here, and not using custom hibernate mappings - just straight GORM. Thanks Burt, I meant to add a note saying that I do have other tables with TEXT columns and they work fine when using straight GORM or criteria.

So how do you use addScalar from your domain class? Can you simply use the mapping property?

static mapping = {
columns {
postCode type:’text’
}
}

Note, I’m working with Grails here, and not using custom hibernate mappings – just straight GORM.

]]> By: Burt Beckwith http://www.javathinking.com/2008/04/no-dialect-mapping-for-jdbc-type-1/comment-page-1/#comment-367 Burt Beckwith Tue, 22 Apr 2008 19:59:01 +0000 http://www.javathinking.com/?p=85#comment-367 A coworker just hit this same problem the other day. The suggestion on the page you cited to use addScalar worked fine for him - it just tells Hibernate that the column is a String type. It's only a problem with SQL queries, and you don't show your SQL, but you can select individual columns using HQL (e.g. reporting queries) and I'm pretty sure this isn't a problem with HQL queries. A coworker just hit this same problem the other day. The suggestion on the page you cited to use addScalar worked fine for him – it just tells Hibernate that the column is a String type. It’s only a problem with SQL queries, and you don’t show your SQL, but you can select individual columns using HQL (e.g. reporting queries) and I’m pretty sure this isn’t a problem with HQL queries.

]]>