Thanks, (that's my SO question), but that doesn't answer definitely whether the range query is broken or not. The comma operator seems to work ok, but what about the range operator?
FWIW I created an issue for the range query problem, including all of the info here: https://github.com/orientechnologies/orientdb/issues/5666 On Monday, February 1, 2016 at 9:20:39 AM UTC-7, SavioL wrote: > > Hi, > in this link > http://stackoverflow.com/questions/35093409/collection-method-broken-in-2-1-9-for-ranges > > there is a possible answer. > > Il giorno venerdì 29 gennaio 2016 21:22:11 UTC+1, Keith Freeman ha scritto: >> >> I've got these classes in my schema: >> >> create class hour extends V >> create class minute extends V >> create class tdindex extends V >> >> create property hour.hour integer >> create property hour.minute linkmap minute >> >> create property minute.index linkset tdindex >> >> >> >> >> When I query single values from 'hour' linkmap I get different 'minute' >> records than when I query ranges: >> >> >> orientdb {db=rawxp}> select expand(minute[29]) from hour where hour=7 >> >> ----+-------+------+----- >> # |@RID |@CLASS|index >> ----+-------+------+----- >> 0 |#13:449|minute|[281] >> ----+-------+------+----- >> >> 1 item(s) found. Query executed in 0.002 sec(s). >> orientdb {db=rawxp}> select expand(minute[30]) from hour where hour=7 >> >> ----+-------+------+----- >> # |@RID |@CLASS|index >> ----+-------+------+----- >> 0 |#13:450|minute|[289] >> ----+-------+------+----- >> >> 1 item(s) found. Query executed in 0.002 sec(s). >> orientdb {db=rawxp}> select expand(minute[29-30]) from hour where hour=7 >> >> ----+-------+------+----- >> # |@RID |@CLASS|index >> ----+-------+------+----- >> 0 |#13:448|minute|[287] >> 1 |#13:451|minute|[283] >> ----+-------+------+----- >> >> 2 item(s) found. Query executed in 0.002 sec(s). >> >> >> >> Isn't that a bug? Or am I misunderstanding how the range query is >> supposed to work? >> >> When I take a look at the records, #13:449 and #13:450 are indeed the >> correct results that I'd expect for that last query. >> >> I tried to attach the DB to this issue (zipped it's 29M), but the upload >> page kept failing with "There was an upload error. Please try again..." >> >> -- --- 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.
