|
|
|
It would be great if you'd stop linking to your blog on our systems.
Actually, how can I turn this feature of in JIRA? I've never seen it before...
OK, got it. Stupid kiddie trackback stuff. I wonder what they'll invent next year... newsgroups maybe.
Tell me about it; it's a combination of the trackback feature of JIRA, and the auto-discover-trackbacks-to-ping feature of Moveable Type.
Nuke the links if you want; I'll try and stop them in the future. I've gone back to the EJB group on this one, and apparently no-one agrees with me that aliases should not be supported in DELETE and UPDATE. So we need to add support for this.
Another thing we need to consider is deletes against an entity participating in a many-to-many. There'd never be a way to bulk delete these (provided the association table contained actual FKs)...
I agree that this is difficult in general, and my understanding is that everyone considers this is out of the scope of the bulk delete feature. There is now some active discussion on this stuff in the group.
At the least, Gavin, I think the lifecycle needs to become explicit. From a Hibernate perspective, I've also got concerns (though I haven't had a chance to prove or disprove) about the impact on objects in the second-level cache; we already have issues where external database calls can corrupt our cache because the objects are deleted, and I'd hate to think that the bulk delete has this effect as well.
Currently it does not clean up the second level cache. However, I have a JIRA task already to implement this.
http://opensource.atlassian.com/projects/hibernate/browse/HHH-352 Also note that its easy enough for you to do this manually in the meantime, using SessionFactory.evict()
from-element aliases are now supported as optional in the bulk dml operations
Just to clarify a bit further. As long as only one "from element" appears in the from clause, aliases are now completely optional in any hql statement, whether DML-style statement or select statement.
| ||||||||||||||||||||||||||||||||||||||||||||||||
I'll see about getting that changed in the spec.