gorm

I am trying to execute a raw sql query using something similar to def dataSource; Sql sql = new Sql(dataSource); But, it seems that this runs in a separate transaction of its own. It therefore misses all the (uncommitted) changes done before it in the service method. What is the best way to run a raw sql query in the current transaction? The above code would create a new connection, hence a new transaction. You can use the current Hibernate session(injecting sessionFactory) to execute a raw sql in the current transaction as below. def session = sessionFactory.getCurrentSession() def results =

If I want to use a domain class, e.g. MoneyTransaction, for two entirely different purposes, i.e.: 1) when a customer places an order 2) when a member gets paid such that I have something like: class Order { static hasMany = [transactions: MoneyTransaction] } class Member { static hasMany = [payments: MoneyTransaction] } and class MoneyTransaction { static belongsTo = [order: Order, member: Member] static constraints = { order(nullable: true) member(nullable: true) } } and then in essence only use one belongsTo/association at a time, is this pretty "standard" usage, or do I need to switch this

I tried to override the dynamic method addTo* provided by Grails/GORM but it doesn't seem to work. Here is the code : class Match { static hasMany = [players: Player, matchPlayers: MatchPlayer] void addToPlayers(Player player) { if (players.add(player)) { MatchPlayer matchPlayer = new MatchPlayer(match: this, player: player) matchPlayers.add(matchPlayer) } } } ma = new Match().save() ma.addToPlayers(player1) The issue is that when calling addToPlayers I got the following exception: java.lang.NullPointerException: Cannot invoke method add() on null object So basically it seems that I have to

I am using the table per subclass strategy in Grails by setting the tablePerHierarchy property of the static mapping field in my superclass to false. This way, Grails creates one table for my superclass and one additional table for each of my subclasses. However, while the superclass and subclass records share the same ID (primary key), there are no foreign key constraints to keep them consistent, i.e. it is possible to delete the superclass record, leaving the subclass record in an invalid state. I want to know if there is a setting/property to make GORM address this in some way, e.g. through

Is this possible to convert in createCriteria()? SELECT * FROM node WHERE (node.type = 'act' AND nid NOT IN (SELECT nid FROM snbr_act_community)) LIMIT 10 I know there's a 'in' operator and here's what I have so far: def c = VolunteerOpportunity.createCriteria() def matchingActs = c.list { node { eq('type', 'act') } maxResults(10) } Just want to see if this is possible. Otherwise, I guess this is possible in HQL right? thanks Sammyrulez for the code. got an idea from that. tested it but it didn't work. i fixed it and here's the final working code: def ids = [14400 as long, 14401 as long] def c