Can the tablePerSubclass mapping definition be extended to allow table per concrete class

There is no scope / time to resolve these remaining lower priority issues for 1.2 so moving to 1.3

for 1.2 final only issues considered blocking will now be fixed

Unfortunately, there aren't any updates for this feature so far.

Right now, there are only two types of the three supported hierarchy mappings supported by grails:

• table per class
• table per subclass

The more important and high performance mapping "table per concrete class" is not supported yet. I hope, this will be done in the near future, because this is an important hierarchy mapping feature.

Yes! This is an important feature, in the performance angle looking forward to see this in the upcoming release.

I think it is a very important feature and should be upgraded to 'Major' from a 'Minor'.

I would also upgrade that to a 'major'...