Correct Lookup table population: use contents property, not insert #29
Conversation
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
Lookup tables are populated via the `contents` property in the table definition, not through insert commands. An "empty" pipeline has its lookup tables automatically populated when the schema is activated. Updated: - Workflow Operations: Show contents property for Lookup tables - Insert chapter: Remove Lookup table references, focus on Manual tables - Populate chapter: Correct table showing data entry methods
dimitri-yatsenko
deleted the
claude/revise-operations-section-01DZM7WBqMKF7bBEGmCJSGVK
branch
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.
Lookup tables are populated via the
contentsproperty in the table definition, not through insert commands. An "empty" pipeline has its lookup tables automatically populated when the schema is activated.Updated: