Open timgraham opened 3 years ago
Hello, I am Blathers. I am here to help you get the issue triaged.
Hoot - a bug! Though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here.
I have CC'd a few people who may be able to assist you:
If we have not gotten back to your issue within a few business days, you can try the following:
:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.
This is because CockroachDB treats a unique index and a unique constraint as identical, but in PostgreSQL they are not (even though it always uses a unique index to implement a unique constraint).
This seems like it would get some of the way towards separating constraints from indexes: https://github.com/cockroachdb/cockroach/pull/65825
We have marked this issue as stale because it has been inactive for 18 months. If this issue is still relevant, removing the stale label or adding a comment will keep it active. Otherwise, we'll close it in 10 days to keep the issue queue tidy. Thank you for your contribution to CockroachDB!
Still a valid issue.
Describe the problem
A partial unique index unexpectedly (not matching PostgreSQL) appears in an introspection query that Django uses:
To Reproduce
Expected behavior
To match PostgreSQL,
cond_name_without_color_uniq
shouldn't appear in the result.Environment:
Additional context
The Django test added in https://github.com/django/django/commit/69a585eb878901eedb8809e4fada42e4d7b01b04 fails:
Jira issue: CRDB-3069