Using searchable across domain classes

9 Comments + Add Comment

• 
  Dierk König January 31, 2008 at 9:59 am

  How cool. I very much like the ‘searchable DSL’ !

  Reply
• 
  Chris February 3, 2008 at 2:12 am

  Can you please describe how you made the searchable plugin work under RC4 and later? I did

  grails create-app bookstore
  grails install-plugin searchable

  grails create-domain-class Book

  added some properties and static searchable = true

  grails generate-all Book

  and

  grails run-app

  and get some weird error messages about URL controllers missing an action

  which version of grails did you use to make it work?

  Reply
• 
  Glen Smith February 3, 2008 at 5:43 am

  Hi Chris.

  I was using it under RC3, so I can’t speak for RC4.

  The only issue I’ve had with it was a NullPointerException on startup for which you need a “patch”:http://jira.codehaus.org/browse/GRAILSPLUGINS-220 .

  Other than that had no issues.

  Reply
• 
  Maurice Nicholson March 3, 2008 at 12:53 am

  Hey Glen,

  nice article

  May I suggest writing the query with a builder closure like:

  BlogEntry.search params, {
  queryString(query)
  must(term(“blogid”, blogid))
  }

  This way you separate the user query from your own internal query, so you can monkey with it, eg:

  BlogEntry.search(params) {
  queryString(query, [escape: true, defaultAndOperator: true])
  must(term(“blogid”, blogid))
  }

  which escapes any dodgy characters and makes all terms in the query string required (this is just my example of course – it depends in your requirements as to how you treat user input!).

  Second it allows you to bypass the query string parser for the blogid. Otherwise, if blogid was a word or words, and it’s put into the text query, it would be parsed and when Lucene actually does the query it might not be the query you intended, since it has stripped junk characters removed common words (and/or) etc!

  I would typically map such properties as “un_tokenized”, meaning when they are saved to the index, they are not broken up into tokens (parsed) but instead are stored as complete verbatim text strings (preserving case and all). Then when you use “term” in the query builder, you can pass in the *exact* value you expect and your search will only match those exact values in the index.

  See the Mapping section of the docs for how to achieve this.

  As for the issues you and others have experienced here, I think there all fixed, but please raise issues if not

  Reply
• 
  Glen Smith March 3, 2008 at 5:27 am

  Awesome Maurice. Thanks for the tip. So good to have you back in the community!

  Reply
• 
  Maurice Nicholson March 3, 2008 at 10:10 pm

  Aw, thanks Glen :blush:

  I’m enjoying reading your Gravl stories. It’s a great name too

  Oh BTW I tried saving this comment without first entering my name and hit save and nothing happened. Then I looked in firebug and saw:

  • Property [author] of class [class CommentCommand] cannot be blank

  Aw, thanks Glen :blush:

  I‘m enjoying reading your Gravl stories. It‘s a great name too

  on

  Mon, 3 Mar 2008 22:08

  but I didn’t see the error displayed

  Reply
• 
  Mustafa Sener April 22, 2008 at 11:21 pm

  Hi Glen,
  I tried this example with two other domain classes which are

  class Book {
  Author author;
  String name;
  static searchable = {
  name()
  author(component: true)
  }
  static belongsTo = [Author];
  }

  class Author {
  static searchable = true
  String name;
  String surname;
  static hasMany = [books:Book]
  }

  and I performed following queries

  Book.search(“authorid:1″);
  Book.search(“authorname:Glen”);

  both of these queries does not return anything.

  am I doing any mistakes?

  Thanks…

  Reply
• 
  botna June 10, 2008 at 1:12 pm

  hi Glen
  I want to use searchable in a many to many relationship
  But I failed
  Would you please tell me how to use that if you have any experiance about that
  Thanks a lot

  Reply
• 
  Ali May 11, 2011 at 3:24 am

  Hello,

  I have book hasMany author and author belongsTo company

  I want to search the books for the company x
  Book.search {
  …..
  }

  what i do ?

  Reply