Ah, sorry. I get it. Thanks Luigi. On Wednesday, September 16, 2015 at 9:35:20 AM UTC-6, Luigi Dell'Aquila wrote: > > Hi Curtis, > > yes, of course, I was referring to an eventual fix on our side, not on > client code ;-) > The initial reason for that was about Graph API, in cases when you have > link collections pointing to documents. If you are using Graph API and > these documents are also vertices, you expect to have Vertex instances as > result, not ODocument instances, this is what the fix does. The problem is > that it just supposes it's working on a collection (ignoring that also maps > are iterable) > > Luigi > > > 2015-09-16 17:10 GMT+02:00 Curtis Stanford <[email protected] > <javascript:>>: > >> Hi Luigi. Thanks for your response. I don't understand how a Map could >> behave like an Iterable. I need to look up values on the map with a key, >> which you can't do with an Iterable. I wonder what the initial reason was >> for that change. Why not just return the map instead of explicitly changing >> it to an iterable of the map values? >> >> On Wednesday, September 16, 2015 at 4:34:25 AM UTC-6, Luigi Dell'Aquila >> wrote: >>> >>> Hi Curtis, >>> >>> I think this behavior was introduced by >>> commit b2c9317f7db3dee26a075d186d32c9eaf6803f21 >>> IMHO the fix should consist in writing a Map implementation that behaves >>> like OrientElementIterable, and just add an IF in that method. >>> @laa, @tglman WDYT? >>> >>> Luigi >>> >>> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OrientDB" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > >
-- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
