anonymous wrote : how was Object_B merge operation
I don't really understand the question...but I'll attempt to answer what I think
your asking anyway. ;)
My best guess tells me your question targets my latter post:
SELECT someA FROM A someA, IN (someA.Bs) someB WHERE someB.stuff=<value>
...which pertains to how Hibernate would do the merge of the additional qualifying data
(stuff) into some object (someB) for the traversal (someB.stuff).
Well, as it stands today, Hibernate3 returns proxy objects. So I was thinking that it
wouldn't be a stretch of the imagination to use that concept here in this case.
One might be able to generate proxies that are the extension of the domain object (e.g.,
class B), but which also include attributes that represent the additional qualifying
information (Stuff). So the proxy might have an effective definition that looked like:
class B_proxy {
| List<A> As; // because proxy extends class B
| String stuff; // assuming stuff was a string qualifier
| ...
| }
If this "extended" proxy were returned by the query, then I think it would be
possible to get the "auto-magical access to the additional qualifiers".
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029998#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...