Repository navigation
feat: export create table sql in DAT write specs - #63
Merged
Merged
Conversation
rliao147
marked this pull request as ready for review
October 9, 2026 20:47
OussamaSaoudi
approved these changes
Oct 9, 2026
OussamaSaoudi
left a comment
Collaborator
There was a problem hiding this comment.
just one comment.
This file contains hidden or 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
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.
Description
SQL harnesses currently reconstruct CREATE TABLE statements from the corpus schema. Export an optional createSql template using the same SQL the generator executes, with {{table}} as the destination placeholder. Retain structured fields for DAT harnesses that don't use SQL.
How was this patch tested?
Does this require an update to the documentation?
No