10

I ran across the and I am not sure if it is needed. You would think these questions would be tagged with and but the "LIKE" tag wiki states:

This tag is not for the SQL reserved keyword LIKE.

I am guessing that since the specifically states this is not for SQL that resulted in the fabulous tag.

I have a few questions about this tag and what steps we should take with it:

  • Do we burninate ?
  • Should we have specific RDBMS "LIKE" tags? This could lead to , etc.
  • Can we just expand the tag wiki of to include SQL?
  • Or should a sql specific "LIKE" tag be created? At this time, there are also other tags which are sql based for like including and .

The has 240 questions so possibly that should become the sql "like" tag and the others (except ) are burninated.

Thoughts?

Improve this question
7
  • 3
    Some of the other "SQL keywords that need to be disambiguated" follow the pattern of sql-foo, so sql-like might be better here than like-keyword/like-operator. But yes, otherwise murder mysql-like with extreme prejudice.
    – Charles
    Mar 31, 2013 at 21:26
  • 2
    The like tag needs to be burninated as well, while we're here.
    – animuson StaffMod
    Mar 31, 2013 at 21:45
  • I'd suggest renaming the original like to social-like
    – Destrictor
    Apr 1, 2013 at 0:36
  • Related: meta.stackexchange.com/questions/104023, meta.stackexchange.com/questions/142241
    – Pang
    Apr 1, 2013 at 0:51
  • @Destrictor the process for that has already been started, the relevant questions are being disambiguated by using facebook-like.
    – slugster
    Apr 1, 2013 at 2:25
  • @slugster I get the idea that that will encourage people to use google+-like and other similar tags as well though =/.
    – Destrictor
    Apr 1, 2013 at 13:24
  • @Destrictor Yeah, that's what I mentioned in the comments on my answer - if there is a vendor or technology specific like that works differently then it should have its specialised tag, so currently we would have facebook-like, google-like, sql-like (assuming that there are legit dev questions related to the google like).
    – slugster
    Apr 1, 2013 at 23:56

2 Answers 2

Reset to default
5

The urban dictionary defines burniate as:

A complete meltdown.

I say we completely melt down this tag as it's simply not specific. Otherwise, we may as well create a tag for each DBMS and it's respective operators. A tag would definitely be more appropriate.

Update

I've retagged all to and have requested that the OP's of questions with request a synonym added of . How do I get a mod to burniate this tag?

Improve this answer
5
  • 2
    I do agree the tag should be renamed to sql-like instead of mysql-like
    – Hugo Dozois
    Apr 2, 2013 at 14:43
  • Once there are no questions tagged with mysql-like the tag will disappear on its own
    – Taryn
    Apr 2, 2013 at 18:50
  • Please do not request an outright burnination and then leave it at that - there is still a lot of facebook-like tags to do, and typically those users have no clue how to tag let alone retag. As mentioned by bluefeet the tag will disappear once it isn't used (i.e. when the work is done).
    – slugster
    Apr 2, 2013 at 19:13
  • 1
    @slugster I believe he was referring to the mysql-like tag none of the others
    – Taryn
    Apr 2, 2013 at 19:37
  • @bluefeet If so then I think the correct approach is to request a synonym, so mysql-like gets automatically matched to sql-like?
    – slugster
    Apr 2, 2013 at 22:13
4

As one who has spent a good amount of time cleaning up a particular like tag, I think we should keep the specific variants and blacklist the generic term (as per animuson's comment).

Some form of the tag needs to remain because people want to talk about it, and it is a reserved keyword in ANSI SQL.

Outright burnination of may be too extreme and dramatic - you will find in many of the instances there are precious few other tags.

So don't get rid of , set your sights on instead. And be prepared - it's a long process to clean it up.

Improve this answer
3
  • I understand getting rid of like, but should we have a database specific mysql-like tag or should there be a sql-like instead? There would be no need to have mysql-like, sql-server-like, oracle-like, etc
    – Taryn
    Apr 1, 2013 at 9:49
  • 2
    @bluefeet Agreed - unless the product specific like works differently then we should be able to cover them all with just sql-like.
    – slugster
    Apr 1, 2013 at 9:51
  • 2
    sql-like + RDBMS tag seems like a good way to do it to me
    – Ben Brocka
    Apr 2, 2013 at 14:53

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