Hi Luca, Sure.
However, I can't download 1.6.3. I filled out the form, but it doesn't send me the download link via email. Regards, Markus On Saturday, 4 January 2014 08:54:51 UTC+1, Markus Menner wrote: > > Hi guys, > > I'm using OrientDB 1.6.2 with the ObjectDatabase. > > I noticed following strange behavior of queries: > > 1.) > Class A, with let's say property status, which is a string. > Add some instances to the db, which contain either "NONE" or "STARTED" in > the status. > > SELECT * FROM A WHERE status IN ['NONE', 'STARTED'] will produce the > correct result (those instances). > > 2.) > Create a property of type String and an index (NOTUNIQUE) on it. > > SELECT * FROM A WHERE status IN ['NONE', 'STARTED'] will produce an empty > result! > > However > > SELECT * FROM A WHERE status='NONE' will produce an NON-empty result with > the correct instances (and I presume also uses the index). > > If you just remove the index (leave the attribute), everything works as > expected. > > So somehow the IN doesn't work as soon as there is an index on a property? > > Kind regards, > Markus > -- --- 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/groups/opt_out.
