You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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!
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.
The text was updated successfully, but these errors were encountered: