-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[rdb] DB metadata extractor #19
Comments
We also want to use the inspection to store a history of the source DB schema. To track and detect schema evolution (eg. new table columns got added). Simply by keeping a textual representation of the inspected DB schema in git. For this, a textual representation (independent of the DSL) should be dumped as well. |
On branch One not so practical way of running the sample outside of Eclipse is currently Running the The content of the generated DSL output file foobar-sources.xrm for this sample looks like this: Right now the output is all on one line, because we haven't implemented formatting rules yet #10 The output is missing |
I'm shelving this to the backlog for now due to inactivity. For a customer project, I used a more pragmatic ad-hoc approach in the meantime: Instead of using the serializer of the DSL, I explicitly generate output in DSL syntax. One advantage of this approach is flexibility, for example to easily serialize addititional metadata from the DB, like column datatypes and comments as |
Inspecting DB metadata in order to reduce the work for the user to define
SourceGroup
/LogicalSource
manually.Approach: Read out DB metadata, build AST model and serialize to the DSL.
Goal: A standalone CLI tool that reads out DB metadata, generates the appropriate EMF object model for a
SourceGroup
and then serializes into DSL text.xrm-cli -extract-sources -rdb db.properties > foobar-sources.xrm
For db.properties, we re-use Stardogs properties for mappings https://www.stardog.com/docs/#_available_properties:
For serializing to the DSL, is has to be considered that naming rules for the identifiers are strict. See Handling invalid identifiers for how this is handled.
The text was updated successfully, but these errors were encountered: