Well CI isn't being nice to me.

memorydb failed. It behaves like anydbm, so I have a fix deployed.
changeset:   6432:97a45bfa62a8

mysql and postgres both failed. For mysql it looks like it's not
seeing a unique constraint error. I have no logged messages.

For postgres, it looks like entering the duplicate row messes
up the db handle, so my attempt to perform a query against the db
to find the active entry throws a:

    psycopg2.errors.InFailedSqlTransaction: current transaction is 
aborted, commands ignored until end of transaction block

on the cursor. Ralf can you take a look at this one? Is it related
to your work in using a cursor rather than a non-cursor?

See https://www.travis-ci.com/github/roundup-
tracker/roundup/jobs/511673688 for the error tracebacks for error
output for all cases. Postgres is at the end.