The first part, yes (I'm just stating my understanding that properties defined in the schema that are not added to a record incur no overhead). The second part is new--whether there is a difference between not adding a property and setting it to NULL. In MSSQL, for example, there is no difference, but my experimentation with ODB suggests that there is. So the question is whether an INTEGER (for example) property set to NULL takes up the same storage space as the same property set to 12345.
On Mon, Jun 6, 2016 at 1:11 AM, 'scott molinari' via OrientDB < [email protected]> wrote: > Didn't Andrey answer that question with the last answer? > > Do you mean whether we add additional information to record if field is >> absent in record itself but defined in schema, do not you ? No, we do not >> add any overhead. > > > Scott > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "OrientDB" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/orient-database/Usr1haixKQc/unsubscribe. > To unsubscribe from this group and all its topics, 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.
