Hi guys, Oversize is per class setting, but is computed per record. So if you do this:
INSERT INTO Employee set name = 'Luca' And the record is, for example, 100 bytes, with oversize 2, it means OrientDB will store 200 bytes with 100 bytes padding. Any further update where the new size is <= 200 the record is just updated, otherwise will be stored on a new space (with space to reuse). In the future we could change the underlying storage, so this oversize technique could be ignored. I suggest you to check with different settings if oversize takes pros to your use case or not. Best Regards, Luca Garulli Founder & CEO OrientDB <http://orientdb.com/> On 28 May 2016 at 19:35, 'scott molinari' via OrientDB < [email protected]> wrote: > All questions I'd like to know the answer to too. > > Scott > > -- > > --- > 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.
