[dna-issues] [JBoss JIRA] Commented: (DNA-37) Federate schema information from relational sources
[
https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin....
]
Sergiy Litsenko commented on DNA-37:
------------------------------------
I agree that the #1 approach is not flexible.
As you've mentioned database metadata object types are pretty stuctured and stable
(TABLE, VIEW, SP, etc).
So, the #2 (node types + mixins) is my favorite choice too.
Mixins could be very important for us for example, when representing graphs to clients
(plus using business rules like DROOLS, etc) in different ways or projections.
BTW, Jackrabbit has flexible and extensible way to define node types without worrying
about fact is it it structured or not.
An example:
<nodeType name="my:RootObject" isMixin="false">
<supertypes>
<supertype>nt:hierarchyNode</supertype>
<supertype>mix:referenceable</supertype>
</supertypes>
</nodeType>
<nodeType name="my:MyMixin" isMixin="true">
<propertyDefinition name="my:myProperty"
requiredType="String" autoCreated="false" mandatory="false"
onParentVersion="COPY"
protected="false" multiple="false" />
</nodeType>
<nodeType name="my:ChildObject" isMixin="false">
<supertypes>
<supertype>my:RootObject</supertype>
<supertype>my:MyMixin</supertype>
</supertypes>
<propertyDefinition name="*" requiredType="undefined"
autoCreated="false" mandatory="false"
onParentVersion="COPY"
protected="false" multiple="false"/>
<childNodeDefinition name="*"
defaultPrimaryType="my:RootObject" autoCreated="false"
mandatory="false"
onParentVersion="COPY"
protected="false" sameNameSiblings="false">
<requiredPrimaryTypes>
<requiredPrimaryType>my:RootObject</requiredPrimaryType>
</requiredPrimaryTypes>
</nodeType>
Federate schema information from relational sources
---------------------------------------------------
Key: DNA-37
URL: https://jira.jboss.org/jira/browse/DNA-37
Project: DNA
Issue Type: Feature Request
Components: Connectors
Reporter: Randall Hauch
Assignee: Sergiy Litsenko
Priority: Minor
Fix For: 0.4
Create a connector for the federation engine that contributes and exposes the database
schema information for a relational database (via JDBC) into the federated repository.
This would make it possible to have a repository provide information about the databases
in an organization. One choice would be whether to import (and copy) the schema
structure, or to provide access to it in real time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira