8

Back in 2013 we decided that and are two different things and questions about such should be tagged separately.

Today Postgres has insert ... on conflict, and has mostly historical Postgres questions, while new questions about "insert ... on conflict" are for the most part not tagged with any specific tag about this feature.

One view is that tags should be more generic so that users not knowing exactly what they are looking for can find things -- for example users knowing syntax/concept/feature from one DBMS looking for help about that on another, bearing in mind that searching for a specific DBMS often requires eg "Postgres" or . In this scenario we could make and synonyms, and add something like as a synonym too.

In the other view we keep tags as specific as possible, probably with links to other tags in their descriptions and wiki entries. In this case we add as a separate tag, and all questions about "inserting if new, updating if existing" on modern versions of Postgres should probably be tagged with this.

0

2 Answers 2

Reset to default
6

I'd be inclined towards the latter - keep the tags as specific as possible.

Then, if a user isn't sure/makes a mistake/whatever, it'd most likely be picked up by experienced users who could add/delete the relevant tags!

Just my €0.02 (pity there's no € cent symbol...)

0

I don't know that I would like to do the synonyms, but I like for sure.

While there may be mostly postgres questions, the concept of a isn't particularly only-postgres

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .