More info on Grails 0.6 release

Jason Rudolph has written a more informative post about Grails 0.6 and its feature set.

It’s also worth noting that there is a very important change to delete cascade behaviour in 0.6.

Namely, if you have no belongsTo on your domain classes, the behaviour will change to never delete referenced classes. Prior to 0.6 this was the opposite – no belongsTo meant your class was the owner in a relationship and all referenced classes would be deleted. This was rather surprising if not alarming behaviour.

However this change means that if you fully understood this counter-intuitive mechanism previously that your applications when upgraded to 0.6 may no longer delete referenced classes without you explicitly setting the belongsTo on the referenced classes.

Generally no data loss is better than data loss, but if you’re deleting financial transactions you might feel differently!