I faced similar problem.. Just try re-building indexes. On Friday, 5 June 2015 13:55:10 UTC+5:30, MV-dev1 wrote: > > OK, I must not be getting enough sleep because this is just too strange. > > Please explain. > > *Repro*: > > 1. I load a MSSQL table via ETL and I didn't previously create the > class... > 2. I try to select all vertices with a certain id (INTEGER) > >> *SELECT PlayerId, PlayerName FROM Player WHERE PlayerId = 99* >> > > *Expected*: get back my single VERTEX > *Actual*: I get back nothing > > *Now the weird part....* > > 3. I select with a range and get back the record > >> *SELECT PlayerId, PlayerName FROM Player WHERE PlayerId >= 99 AND >> PlayerID <= 99* >> > > And, because a picture is worth a thousand words... > > > <https://lh3.googleusercontent.com/-sW0MwLXdgdo/VXFb4wWplQI/AAAAAAAAAFU/BMAlU5RloFU/s1600/OrientDB-SELECT1.jpg> > > > And here is the schema > > > > <https://lh3.googleusercontent.com/-9wgRVSyrxrI/VXFcZDy6qdI/AAAAAAAAAFc/IL1_vq6Yw48/s1600/OrientDB-SELECT2.jpg> > > >
-- --- 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.
