Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Migrations hang when "default=" is set on a new field, while USING HASH.
See original GitHub issueIssue Description
What works.
First time table creation, and most other migrations work fine.
What does not work.
Migrations hang when default= is set on a new field, while USING HASH in the table.
message = models.TextField(default='') # Hangs migration.
message2 = models.TextField(null=True) # Works.
Issue Details
This issue is mentioned here: https://github.com/django/django/blob/7e3c9c3205e9646261cea5e5a7af7ec0e806690a/docs/ref/migration-operations.txt#L163
I believe, when the migration has to perform a full rewrite of the table, Django cannot understand crdb_internal_id_shard_16 (or how it fits into the model) when USING HASH is specified.
Possible resolution
Is there a way to ignore or hide fields which CockroachDB generates automatically when using hash sharded index?
If we can get Django to simply ignore anything of crdb_internal_* we could be okay.
Related: 78049 https://github.com/cockroachdb/django-cockroachdb/issues/264
Issue Analytics
- State:
- Created 6 months ago
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for this report! Could you share the way of reproducing the bug using only
cockroach sql? And file an issue at https://github.com/cockroachdb/cockroach (or post here, and I can file it for you).Great, thanks. Closing as “not completed” since it’s not applicable to this repo.