fix building primary key with autoincrement #2185
Merged
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.
Based on this issue #2180 , the video shows that editing is disabled due to the lack of primary key, not after adding an
enum
column. It's disabled even before adding anenum
column.But after testing the table builder, I found that creating a column as a pk with
autoincrement
doesn't make the column pk. Thus the editing was disabled in the first place.Note: There's no auto increment functionality for a PK in BigQuery and Cassandra DBs.
close #2180