I tried to follow the discussion, but it went from storing field names and 
serializations of classes, to binary serialization too quickly.
What is a final decision on storing fields for strict class definition?
I am a little afraid on global field catalog, for a cases where millions of 
records created with schema free layout and system looking up and creating 
new fields in catalog for each record. Schema full class definition vs 
Schema free class definition sounds like perfect solution.
Are you still considering it for 2.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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to