Hi, thank you for the database and test query in form of query. The problem was on LET that in case the index was used, the optimization path called it after the projections were already done.
Fixed in "develop" branch (1.7-SNAPSHOT). Lvc@ On 2 April 2014 23:18, MrFT <[email protected]> wrote: > > Here's the database again, so you can check what the problem could be. > > http://we.tl/w7S4dB3pbn > > Again, link will only be valid for 1 week. > > > > Op woensdag 2 april 2014 22:10:11 UTC+2 schreef MrFT: > >> >> >> It does have an x, it's just not a list like in the other records >> >> (which is something else that is quite confusing, wouldn't it make more >> sense that it is always a list, even if there's only 1 element? But that's >> beside the current issue) >> >> >> >> >> Op woensdag 2 april 2014 22:03:31 UTC+2 schreef Lvc@: >>> >>> Hi, >>> in the second example, the 2nd record has no x as well. >>> >>> Lvc@ >>> >>> >>> >>> On 2 April 2014 21:15, MrFT <[email protected]> wrote: >>> >>>> select key as key, *$x as x*, outE()[ @class = has_property ] as outE >>>> from School *let x = *outE()[ @class = has_property ] >>>> where key = 'a2a40e3c-a3a4-11e3-ace8-005056872b95' >>>> >>>> >>>> Doesn't work, as in, doesn't return the column x. It returns >>>> >>>> { >>>> "@type": "d", >>>> "@rid": "#-2:1", >>>> "@version": 0, >>>> "key": "a2a40e3c-a3a4-11e3-ace8-005056872b95", >>>> "outE": "#26:7685" >>>> } >>>> >>>> >>>> select key as key, $x as x, outE()[ @class = has_property ] as outE >>>> from School let x = outE()[ @class = has_property ] >>>> >>>> (same without the where clause) does work. It returns records like: >>>> >>>> { >>>> "@type": "d", >>>> "@rid": "#-2:1", >>>> "@version": 0, >>>> "key": "a2a3e1be-a3a4-11e3-ace8-005056872b95", >>>> "x": [ >>>> "#26:7669", >>>> "#26:7670" >>>> ], >>>> "outE": [ >>>> "#26:7669", >>>> "#26:7670" >>>> ], >>>> "@fieldTypes": "x=e,outE=e" >>>> }, >>>> { >>>> "@type": "d", >>>> "@rid": "#-2:2", >>>> "@version": 0, >>>> "key": "a2a3e6aa-a3a4-11e3-ace8-005056872b95", >>>> "x": "#26:7671", >>>> "outE": "#26:7671" >>>> }, >>>> { >>>> "@type": "d", >>>> "@rid": "#-2:3", >>>> "@version": 0, >>>> "key": "a2a3e8da-a3a4-11e3-ace8-005056872b95", >>>> "x": [ >>>> "#26:7673", >>>> "#26:7672" >>>> ], >>>> "outE": [ >>>> "#26:7673", >>>> "#26:7672" >>>> ], >>>> "@fieldTypes": "x=e,outE=e" >>>> }, >>>> >>>> >>>> I defined the property 'key' and an index on 'key' on the super-class >>>> of School, which is called OrganizationalUnit. >>>> >>>> Can that be the reason for the problem? >>>> >>>> What should I do to solve this? >>>> Or is it a bug, and should it have worked correctly (I would assume >>>> that it should work)? >>>> >>>> -- >>>> >>>> --- >>>> 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. >>>> >>> >>> -- > > --- > 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. > -- --- 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.
