Dear Luigi, will it break DB files compatibility then? Maybe it is better to have such dramatic change before v3.0 is out (fix it while moving from v2.x to 3.0), to make migration to next 3.X versions smoother?
On Tuesday, February 6, 2018 at 1:46:53 PM UTC+5, Luigi Dell'Aquila wrote: > > Hi Chris, > > Yes, it's something we already considered. We couldn't manage to refactor > it in v 3.0 just for a matter of priorities, but I can tell you that we > will do it soon > > Thanks > > Luigi > > 2018-02-06 2:18 GMT+01:00 cm-perrs <[email protected] <javascript:>>: > >> Hi, >> >> We are using OrientDB as document database in plocal mode. Classes are >> schema-mixed. We manage cluster selection by some record fields such as >> timestamp, using doc.save(clusterName). >> >> When looking inside cluster PCL files I find that every record has the >> class name as a string. This has a massive impact on the size of the file >> when the record is small. >> >> Why is class name saved with every record? The cluster belongs to the >> class by oClass.addCluster(clusterName), so maybe the class name in the >> record is redundant? >> >> Thanks, Chris >> >> -- >> >> --- >> 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.
