[Junie]: Junie inspectdb creates a redundant unique_together for composite primary keys

[junie-eap]

📌 Hey! This PR was made for you with Junie, the coding agent by JetBrains Early Access Preview

It's still learning, developing, and might make mistakes. Please make sure you review the changes before you accept them.
We’d love your feedback — join our Discord to share bugs, ideas: here.

• 🔗 Issue: Junie inspectdb creates a redundant unique_together for composite primary keys #3
• 🏷 Title: Junie inspectdb creates a redundant unique_together for composite primary keys

📝 Original Issue Description

  Issue task:
  Description 

With the following table:

CREATE TABLE example (
a integer,
b integer,
c integer,
PRIMARY KEY (a, c)
);
Running inspectdb produces the following model definition:

class Example(models.Model):
pk = models.CompositePrimaryKey('a', 'c')
a = models.IntegerField()
b = models.IntegerField(blank=True, null=True)
c = models.IntegerField()

class Meta:
    managed = False
    db_table = 'example'
    unique_together = (('a', 'c'),)

I'm pretty sure the last unique_together = (('a', 'c'),) is redundant since the pk = models.CompositePrimaryKey('a', 'c') already implies uniqueness, no?

  Issue comments:
  No comments yet

📊 Junie Summary

The inspectdb command in Django was modified to prevent redundant unique_together constraints for models with composite primary keys. The implementation was successful, ensuring correct handling of unique constraints, with all tests passing.