Comments on: Some workarounds for a few Grails 1.1.x bugs http://www.anyware.co.uk/2005/2009/06/23/some-workarounds-for-a-few-grails-11x-bugs/ Grails, Apple, usability and world stuff Thu, 26 Jan 2012 17:27:44 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Daniel Rinser http://www.anyware.co.uk/2005/2009/06/23/some-workarounds-for-a-few-grails-11x-bugs/comment-page-1/#comment-145729 Daniel Rinser Sun, 09 Aug 2009 12:58:16 +0000 http://www.anyware.co.uk/2005/?p=477#comment-145729 Just a small "bugfix": "Author.list().collect { it -> it.book == null }" should be "Author.list().findAll { it -> it.book == null }" (or grep {...}). Your code would return a list of booleans (one for each author, indicating if she has a book). Just a small “bugfix”:

“Author.list().collect { it -> it.book == null }” should be “Author.list().findAll { it -> it.book == null }” (or grep {…}). Your code would return a list of booleans (one for each author, indicating if she has a book).

]]> By: Tom http://www.anyware.co.uk/2005/2009/06/23/some-workarounds-for-a-few-grails-11x-bugs/comment-page-1/#comment-141192 Tom Thu, 25 Jun 2009 22:04:46 +0000 http://www.anyware.co.uk/2005/?p=477#comment-141192 "It is currently impossible to query for null associations on 1:1 relationships using any mechanism - criteria, dynamic finders, HQL all return empty results." My workaround is to fall back to groovy.sql.Sql for queries that are too complex for Hibernate. “It is currently impossible to query for null associations on 1:1 relationships using any mechanism – criteria, dynamic finders, HQL all return empty results.”

My workaround is to fall back to groovy.sql.Sql for queries that are too complex for Hibernate.

]]> By: Raphael http://www.anyware.co.uk/2005/2009/06/23/some-workarounds-for-a-few-grails-11x-bugs/comment-page-1/#comment-141053 Raphael Wed, 24 Jun 2009 15:00:13 +0000 http://www.anyware.co.uk/2005/?p=477#comment-141053 I'd like to add this tip http://blog.xebia.com/2009/03/20/hsqldb-database-already-in-use-by-another-process-exceptions-on-linux/ I like keeping a console with grails interactive running for testing(hsql:mem), and another shell with the application running in dev mode(hsql:file) but hsql complains about a file lock, even when running a memory DB. Version 1.8.0.10 fixes this. I’d like to add this tip http://blog.xebia.com/2009/03/20/hsqldb-database-already-in-use-by-another-process-exceptions-on-linux/

I like keeping a console with grails interactive running for testing(hsql:mem), and another shell with the application running in dev mode(hsql:file) but hsql complains about a file lock, even when running a memory DB. Version 1.8.0.10 fixes this.

]]>