Tag Info

I agree. The sql tag is just too generic. Having the following tags should be sufficient enough to tag questions correctly with whatever Structured Query Language Dialect/Programming Language is ...

The sql tag has now been burninated. It has also been blacklisted. (technically, marked intrinsic, so inbound migrations are not blocked; the tag is removed during migration). Thanks to everyone ...

I am both for and against this proposal, so ±1   🙃 For / 👍 / Agree / 😺 Yes, the sql tag by itself is currently quite ambiguous. And not just because it's what you ...

I think the misusage of the tag schema stems from people not reading the tag's usage guidance or the (non-existant) tag wiki excerpt. There there is the ambiguity of the tag schema itself, because of ...

Against - SQL is not the only query language in existence. For OLAP we have MDX, for various NoSQL solutions we have different proprietary query languages. SQL and PL/SQL are not the same thing on ...

Can we burninate the [truncation] tag? Yes you can get rid of truncation by manually retagging the existing 13 questions to not use it. The truncation tag will be deleted by the system within 24 ...

I absolutely agree that truncate and truncation are overloaded terms on their own, even when limiting their usage strictly to databases. However, should these tags really just go? It may still be ...

In my opinion, burninating a tag should be reserved for tags that are causing a current and ongoing problem around usability of the site. My vote would be to leave them in since the harm of doing so ...

I think it would be useful to retain a tag for the language for those odd times when someone has a question about the standard, or some aspect of the language that works across many database-...

For Burninantion. I am still for burnination, but think the RDBMS tag is not sufficient and I certainly do not think all query-questions for PostgreSQL should be tagged pl/pgsql, nor pl for Oracle. ...