Hi!

I have more concern about Collection and Map
projection: is this query easy to implement?

select distinct employees from Department where ...

At least I don't know how a SQL datastore could
compare the collections one another.

So, maybe we should discribe more on Collection
and Map projection, or simply specify that their
distinction is the same as their owner objects,
dispite whether they equal one another.

--- erik@jpox.org wrote:

> Thanks for the comments, I agree with you all.
>
> Regards,
>
> Quoting Michael Bouschen <mbo.tech@spree.de>:
> 
> projections of 
> query would return the 
> result would be a list 
> for projections of 
> but AFAIK the current 
> whether projecting a 
> result that iterates the 
> employees.contains(e) 
> employees, so for each 
> collection. Query (2) 
> employee is included in 
> department. 
> return Map.Entry 
> map or it iterates the 
> is no contains for maps. 
> would 
> map 
> field. 
> but in 
> in 
> result 
> of 
> map 
> the 
> automatic 
> cells 
> (key, 
> the 
>  ________________________________________
__________ 
> protection around 
>
>
>
>


 ________________________________________
__________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[ Post a follow-up to this message ]