Skip to content
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

ID to Link KAPE Target File and SQLECmd Map #699

Open
weslambert opened this issue Oct 5, 2022 · 1 comment
Open

ID to Link KAPE Target File and SQLECmd Map #699

weslambert opened this issue Oct 5, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request repo housekeeping Relates to housekeeping of this repo

Comments

@weslambert
Copy link

Is your feature request related to a problem? Please describe.
Currently, we have to rely on comments to link a SQLECmd map file to a KAPE target file. We do this because we dynamically generate our own language-specific targets from the target files and want to associate the query defined within the SQL map file to the target.

Describe the solution you'd like
It would be great to either share the map/target file's ID in each's definition, or generate a common ID to use for linking the two files.

Describe alternatives you've considered
Keying off of comments. However, this is a bit of a hack, and does not always work as expected.

@weslambert weslambert added the enhancement New feature or request label Oct 5, 2022
@AndrewRathbun AndrewRathbun self-assigned this Oct 30, 2022
@AndrewRathbun AndrewRathbun added the repo housekeeping Relates to housekeeping of this repo label Oct 30, 2022
@AndrewRathbun
Copy link
Collaborator

@weslambert would something standard in the comments like

# Corresponding SQLMap GUID: <GUID here>

alternatively

# Corresponding SQLMap Filename: <.smap filename here>

Would either of these be a solution? Option C? I don't mind doing it, but whatever it is, I'd want it to be uniform amongst all the Targets that pull artifacts that can be parsed by SQLECmd. Let me know yours thoughts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request repo housekeeping Relates to housekeeping of this repo
Projects
None yet
Development

No branches or pull requests

2 participants