changeset 8430:642e6d7d18c4 stable

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.
author Mads Kiilerich <mads@kiilerich.com>
date Fri, 22 May 2020 14:02:55 +0200
parents 04908b44005c
children 0f3a584edcb3
files kallithea/model/db.py
diffstat 1 files changed, 0 insertions(+), 1 deletions(-) [+]
line wrap: on
line diff
--- a/kallithea/model/db.py	Fri May 22 16:54:10 2020 +0200
+++ b/kallithea/model/db.py	Fri May 22 14:02:55 2020 +0200
@@ -2295,7 +2295,6 @@
     __tablename__ = 'user_ssh_keys'
     __table_args__ = (
         Index('usk_fingerprint_idx', 'fingerprint'),
-        UniqueConstraint('fingerprint'),
         _table_args_default_dict
     )
     __mapper_args__ = {}