Error is not precise when 2 database connexions use the same display name

[xavier-GitHub76]

Bug description

Hello

with Superset 3.1.1, Error is not precise when 2 database connexions use the same display name

Regards

How to reproduce the bug

Just create 2 database connexion with the same display name

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[rusackas]

Do you mean to say you'd like it to:

1. Throw an error saying "Database name _____ is in use. Please give your database connection a unique name"
2. Let you name databases with the same name?

I hope you mean (1), as (2) would cause a lot of confusion/problems

[xavier-GitHub76]

Hello,
I mean (1).
In this use case, with a error message more precise (like your proposition "Please give your database connection a unique name"), the user would immediately know that he must change his connection display name.
Best regards