Hi, I'm a bit disappointed about Entity relationships and EJBQL. What used to seem to be simple, now it is a nightmare.
How can I achieve lazy loading of related EBs in Orion? For instance, there's an EB (EB1) that has 1..N relationship to another (EB2). If I lookup an instance of EB1 do all the related instances of EB2 load at the same time, even if I do not need to access them? A bit off-topic (as EJB QL is not available in Orion so it is impossible to develop something general, really portable), but I'm curious about the issue: Do you think that Entity relationships and EJB QL could be as optimized as smart finder methods? I wish I could supply finders with SQL SELECTs... Unfortunately, you have the drawback of EJBQL that you're limited to refer to EBs (abstract schemas). So, a more complex case: I have to model the following situation: M..N relationship between Users and Countries. Each country belongs to one region (region id is a column in the country table). I have to lookup those countries that belong to the regions of the countries mapped to a user. So it's not only a "simple" relationship between users and countries, but I'd need a countr-country 1..N relationship over the region id. Therefore the EJB QL would look like this for a finder method: SELECT OBJECT(rc) FROM User AS u, IN(u.countries) c, IN(c.regionCountries) rc WHERE u.userID = ?1 With one smart SQL SELECT it would be possible to retrieve the result set but how will servers manage the above situation? regards, please give me a hint with the first Orion-specific question, thanks, Tibor
