kallithea Changeset - 642e6d7d18c4

Changeset - 642e6d7d18c4

Parent rev.

Child rev.

[Not reviewed]

stable

0 1 0

Mads Kiilerich - 5 years ago 2020-05-22 14:02:55
mads@kiilerich.com

db: drop double specification of unique constraint (Issue #374)

Consistently use "unique=True" for single column constraints. Only use
UniqueConstraint for composite constraints.

MySQL did not like this double specification, while PostgreSQL and SQLite
did not care.

1 file changed with 0 insertions and 1 deletions:

kallithea/model/db.py

0 comments (0 inline, 0 general)

kallithea/model/db.py

➞

Show inline comments

@@ @@ -2292,13 +2292,12 @@ class Gist(Base, BaseDbModel): @@
 class UserSshKeys(Base, BaseDbModel):
     __tablename__ = 'user_ssh_keys'
     __table_args__ = (
         Index('usk_fingerprint_idx', 'fingerprint'),
         UniqueConstraint('fingerprint'),
         _table_args_default_dict
+    )
     __mapper_args__ = {}
     user_ssh_key_id = Column(Integer(), primary_key=True)
     user_id = Column(Integer(), ForeignKey('users.user_id'), nullable=False)

0 comments (0 inline, 0 general)