[
https://jira.jboss.org/jira/browse/DNA-49?page=com.atlassian.jira.plugin....
]
Randall Hauch updated DNA-49:
-----------------------------
Fix Version/s: 0.7
(was: Future Releases)
Assignee: Barry LaFond (was: Bojidar Penchev)
Complexity: High (was: Medium)
Priority: Major (was: Minor)
Barry has picked up this work, and has developed a very nice sequencer capable of parsing
the more important DDL statements from several different dialects, and constructing a
graph structure that is largely the same for all dialects (though some dialects will
result in dialect-specific properties and maybe nodes). The sequencer attempts to detect
the dialect by running multiple parsers and finding the one with the "best
fit".
One very interesting capability of this sequencer is that, although only a subset of the
(more common) DDL statements are supported, the sequencer is still extremely functional
since it does still add all statements into the output graph, just without much detail
other than just the statement text and the position in the DDL file. Thus, if a DDL file
contains statements the sequencer understands and statements that the sequencer does not
understand, the graph will still contain all statements and those statements understood by
the sequencer will have their full detail. Since the underlying parsers are able to
operate upon a single statement, it is possible to go back later (after the parsers have
been enhanced to support additional DDL statements) and re-parse only those incomplete
statements in the graph.
Support for additional statements and additional dialects will be added in the future
under different issues.
Sequence DDL files
------------------
Key: DNA-49
URL:
https://jira.jboss.org/jira/browse/DNA-49
Project: DNA
Issue Type: Feature Request
Components: Sequencers
Reporter: Randall Hauch
Assignee: Barry LaFond
Fix For: 0.7
Create a sequencer that parses DDL files and generates the subgraph representing the
relational schema. Multiple dialects should be supported, including those for Oracle, MS
SqlServer, PostgreSQL, MySQL, and others. Ideally this could be done with one sequencer
(since most users/admins won't care about which dialect a particular file is;
they'll just want it sequenced).
--
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