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

Download 1159.patch

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.

rebased onto 48d8e28b670ec5212b3c753aa764970ea4409224

rebased onto 2c3ebda9f9f6c93db78a20d7638885f2aa6e08dc

rebased onto 54e515f7ef39a62ba05b8a0aa26ed3fd096148d9

@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 b1237a26c20a521737b3f47429468f71a1f5d6e5

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

Commit 23cd44b5 fixes this pull-request

Pull-Request has been merged by tkopecek

@jcupova - this one is exactly same as #1692 which, I've closed as a dup.

Metadata