Will do - I'm thinking it should be a feature request for a keyword to "preserve null fields". That should allow Orient to remain backwards-compatible with existing queries that expect the current behavior, but provide necessary functionality when the client doesn't want those fields dropped.
On Thursday, December 11, 2014 3:22:08 AM UTC-5, Enrico Risa wrote: > > Hi Bk > > i think is not possible. > Could you raise an issue here > https://github.com/orientechnologies/orientdb/issues ? > > Enrico > > 2014-12-11 3:42 GMT+01:00 BK <[email protected] <javascript:>>: > >> Why does fieldB get dropped in the second query, below? Is it possible >> to preserve it in the results for that query? >> >> (OrientDB-community 1.7.9) >> >> select * from SomeObject where @rid=#13:0 >> ----+-----+--------------------- >> # |@RID |fieldA |fieldB|fieldC >> ----+-----+--------------------- >> 0 |#13:0|"foo" |null |#15:19 >> ----+-----+--------------------- >> >> select *, @rid as id from SomeObject where @rid=#13:0 >> ----+-----+------------------- >> # |@RID |fieldA|fieldC|id >> ----+-----+------------------- >> 0 |#13:0|"foo" |#15:19|#13:0 >> ----+-----+------------------- >> >> -- >> >> --- >> 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] <javascript:>. >> 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.
