koji

Clone

#1159 enforce unique content generator names in database
Merged 4 years ago by tkopecek. Opened 5 years ago by ktdreyer.
ktdreyer/koji unique-cgs  into  master

No commits found

Set a uniqueness constraint on the content generator name in the database.

Prior to this change, we were only enforcing this in the hub application layer. Configure this in postgres for safety.

I noticed this while implementing a new listCGs hub call.
Edited 5 years ago by ktdreyer

rebased onto 48d8e28b670ec5212b3c753aa764970ea4409224
5 years ago

rebased onto 2c3ebda9f9f6c93db78a20d7638885f2aa6e08dc
5 years ago

rebased onto 54e515f7ef39a62ba05b8a0aa26ed3fd096148d9
5 years ago

@ktdreyer I've created #1668 for this - can you update it, please, for 1.19?

I've created new PR for 1.19: #1692

rebased onto b1237a2
4 years ago

Whoops I missed your comment and I did rebase this one.

Commit 23cd44b fixes this pull-request

Pull-Request has been merged by tkopecek
4 years ago

@jcupova - this one is exactly same as #1692 which, I've closed as a dup.
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.