Include column definitions in schema dump if the column name is not id
#173
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.
Mitigates #171 by including primary key columns in the column definition if the primary key is not named
id
. This mirrors behavior prior toddfa259bbec88aefa3eaf2942392b8473a477601
while continuing to omit the primary key column if the name isid
.This is likely only a partial solution that seems like the best short-term path forward. A better long-term solution likely relies on #172 being solved such that passing
id: :TYPE_NOT_UInt32
is respected. This would also need to include non-integer data types such as:datetime
.