MySQL has the "information_schema" database, which contain the metadata for
the actual database.
Does OrientDB internally use a database/tables to store the schema metadata?
If so, is this exposed somehow?
And if so, are you allowed to tinker with this schema?
What I'm thinking is, the Orient data-model is rich enough to support fully
automated generation of meaningful user interfaces for data administration,
even for schema-less data there is type information since we have no
"foreign keys" that are just numbers which need to be defined and resolved.
If I could add, say, a custom datatype-property to the property-schema, I
could designate string-properties as e.g. e-mail address, hex color-code,
IP address, etc. allowing for meaningful user interface generation, input
validation, etc.
Effectively, this would enable us to leverage OrientDB as a kind of CMS.
Of course, I could add my own metadata-table for this information,
associating e.g. "{class-name}.{property-name}" with metadata... but both
class-names and property-names can change, so this would work better if
properties in the schema actually had RIDs to which I could associate these
links.
Anyway, getting ahead of myself here - are properties actually records with
RIDs somewhere underneath the hood, and is there any way to get at this
information?
--
---
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.
