Steve, I see you mention serialization of sub-elements as well.
How much effort do you think it is to get this working for embedded maps and do you see that as something you will look into? Regards, -Stefan On Monday, 7 April 2014 12:25:33 UTC, [email protected] wrote: > > Hi, > > Do you have any rough estimation regarding how much space this could save? > I know the question is very vague but I'm curious to know if you have done > any comparison at all. > > Luca; Are you able to prioritize this to take advantage of this create > work asap? > > Steve, again, thank you very much. > > Regards, > -Stefán > > On Monday, 7 April 2014 03:41:11 UTC, Steve Coughlan wrote: >> >> On 07/04/14 13:12, Steve wrote: >> > For testing/debug it may be convenient to use a string data >> > serialization format. Or if using compressedbits this field may >> > specify which compression algorithm or settings to use. >> >> I should add a caveat to this statement. As long is there is not a >> mismatch between whether the serializer serializes fixed length fields >> using the same fixed length. Some code changes would be required to >> allow for this although they would not be difficult to do. >> > -- --- 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.
