Hi All,
I'm looking for advice on an implementation strategy for annotating
vertexes with arbitrary (i.e. user driven) attributes where the attribute
values may need to carry datatype information.
(Our application is a network storage and sharing system for scientists -
within each network uploaded, the user controls the semantics of their
network. So I don't think I can safely let them create arbitrary vertex
properties at the OrientDB level - I need a layer abstraction)
We are currently handling this with an embedded map property defined for
the tinkerpop VertexFrame class.
public interface IMetadataObject extends VertexFrame{
@Property("metadata")
public void addMetadata(String metadataKey, String metadataValue);
Some of my use cases are now making me re-consider this strategy.
I have a requirement to parse and store XGMML graphs in our schema and for
those networks the attribute values can have stored primitive datatypes.
In the context of the my current implementation, I would wish that I could
mix datatypes on embedded map values. Can I do that if I manage the
embedded map differently?
Or is there a totally different approach that I should consider?
Thanks!
--
---
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/groups/opt_out.
