Hi Goh, thanks for reporting, this seems to be a bug. Could you open an issue about it?
Thanks Luigi 2015-02-13 8:14 GMT+01:00 Siang Hwee Goh <[email protected]>: > Hi, > > Any idea about the SELECT IN problem? > > Cordially, > Goh > > > On Wednesday, February 11, 2015 at 5:44:23 PM UTC+8, Siang Hwee Goh wrote: >> >> Hi, >> >> I am doing some testing on the SELECT IN operation. The is a Employee >> class in the database with 2 columns (Name, Age). Only 1 record had been >> inserted. >> >> INSERT INTO Employee(Name, Age) VALUES ('GOH', 33). The Name property is >> case insensitive. >> >> When I tried to retrieve the record with this statement. SELECT FROM >> Employee where Name IN ['goh','tan'], it returned a correct result. >> However, when I change it to SELECT * FROM Employee where Name IN >> ['GOH','tan'], it returned no result. 'GOH' is the correct result if it is >> case sensitive. In terms of case insensitive, both should also return a >> record. Am I missing out something? Thanks. >> >> Cordially, >> Goh >> > -- > > --- > 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.
