Hello,
I like the possibility to directly store deeply nested objects (documents)
in OrientDB. But the requirement to always specify the type and the class
as attributes within my objects is very inconvenient. I understand that an
object could be either seen as a plain object or a map, and that the DB has
to know which way to go. But I already specified this with the schema of my
object. So why do I have to repeat this with each and every instance? In
the end this is what the schema definition is made for to hold the metadata
independently of its instances.
Take this for example:
"create class validity",
"create property validity.employees string",
"create property validity.old integer",
"create class model",
"create property model.validity embeddedlist validity"
Now if I want to inset a model, I have to specify the type and the class of
the embedded validity object, like so:
var oModel = {
validity: [
{
"@class": "validity",
"@type": "d",
"employees": "Employees",
"old": 802
}
],
};
Couldn't the DB just recognize the intention from the schema definition? I
don't think the specification of metadata with the instance makes sense,
because you normally wouldn't change the type per instance.
--
---
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.
