Make nested EXEC SQL available
#149
Draft
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.
When a file specified by
EXEC SQL INCLUDEcontains additionalEXEC SQLstatements, the correspondingCALLstatements were not generated in the converted output.This pull request addresses and resolves that issue.
When expanding the contents of a file specified by
EXEC SQL INCLUDE, markers are added at the beginning and end in the intermediate file to indicate the range of the included content.In the
ppoutputfunction inppout.c, the intermediate file is read line by line, and processing is performed based on the content of each line. However, if a line contains the INCLUDE start or end marker, it is skipped using continue.To address this, the code was modified to check whether the line with the marker immediately follows an
END-EXEC. line before skipping. If it does, the correspondingCALLstatement is now properly generated.