On Aug 20, 2006, at 10:32 PM, Mike Kienenberger wrote:
I didn't state how a user would configure it, only how it could be processed if it was specified.
Ah, ok.
Right now, I'm leaning on making join semantics represent this. So a query can be (inner|outer) + (split|nosplit). Realistically, that's probably only inner, inner w/split, and outer w/split as the three options.
I guess that's JPA join semantics?
Your original idea of "+" and "|" works as part of the path expression works for me as well.
I don't mind this as an alternative. I just thought it would be cool if we find synergy between EJB QL and our current SelectQuery (and I think we came close). If it turns out that we are stretching it too much, we can use this semantics instead.
Andrus
