RAMI-67: Add database build extension to load and evaluate Puse library SQL folder. #126
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ijoel
changed the title
|
What do you thinking of making this less specific to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Ticket RAMI-67 was created to explore a Triangulum extension that would add database build support to load SQL from a folder on the classpath. Functionality that is required to support loading the required database changes for the common change detection facilities of the Pulse library.
The change adds the
--pulse-datalong cli flag. When specified as part of a database build, Triangulum will search theclasspathfor a pulse SQL folder, then load and evaluate its contents.This is, currently, a work in progress. Supporting changes to the top-sort's "namespace" resolution is needed.
Related Issues
Closes RAMI-67