This is discussed a little bit here as well.

The tag is on almost 1000 questions at this point. It is also useless.

The error code in question is about the most generic error you can get - "There is an error in your syntax"!

If you need help, searching using this tag is useless because the tag is so generic - there's pretty much no way that your issue will be the same as someone else's issue based solely on this error code.

Additionally, a large number of these questions are likely Too Localized since they boil down to syntax errors.

I request that this tag be burninated as useless.

  • 11
    Public Service Announcement: There are only two ways to remove a tag without involving a Stack Exchange Developer: synonymizing the tag with another tag, or removing each tag instance individually. Developers are only involved when it's an emergency.
    – user102937
    Commented Apr 23, 2013 at 14:48
  • 1
    @RobertHarvey Well that changes things somewhat.
    – JNK
    Commented Apr 23, 2013 at 14:50
  • 7
    To add to Robert's PSA, since many of these questions should probably be closed, it's probably worth it to do this tag removal manually. Commented Apr 23, 2013 at 14:51
  • 1
    @BilltheLizard I like that idea!
    – JNK
    Commented Apr 23, 2013 at 14:55
  • Burninating a tag should also be done only if the tag keeps to be used, and there is no way to remove it because there is a new question using it for every question from which the tag is removed. If removing the tag is not successfull, and there is no tags for which it can be made a synonym, then burninating could be requested.
    – apaderno
    Commented Apr 23, 2013 at 15:38
  • 2
    I suspect the total number of down-votes on this request to be either zero or one - but no more than one.
    – Aaron Bertrand Staff
    Commented Apr 23, 2013 at 15:56
  • 2
    Every day there are several new questions posted about this mysql error code, even though hundreds of answers already say "This is a syntax error, check your syntax!". So many people never bother reading the MySQL manual or checking their queries.
    – Jocelyn
    Commented Apr 23, 2013 at 16:27
  • 3
    @Jocelyn That doesn't mean it's an informative tag, though. I'm not sure if you are trying to condone keeping it or not, but that tag adds essentially 0 information to the question. It may as well be "error".
    – JNK
    Commented Apr 23, 2013 at 16:40
  • 3
    @JNK I completely agree with your post here and all explanations given.
    – Jocelyn
    Commented Apr 23, 2013 at 16:41
  • 3
    Maybe we should keep the tag, as it's a honeypot for questions that, being syntax errors, are likely to be too localized and thus close-bait.
    – Charles
    Commented Apr 23, 2013 at 19:20
  • @Charles I'm working on getting them all closed per bill's suggestion
    – JNK
    Commented Apr 23, 2013 at 19:24
  • 1
    Can I get paid in rep to burniate this tag? I'm thinking 200/rep/hour is a fair market rate.
    – Kermit
    Commented Apr 23, 2013 at 19:44
  • 2
    I've got my close votes review queue filter set to 'burninate'. Commented Apr 24, 2013 at 2:50
  • Also discussed here Do we really need a tag for every error code? Commented May 4, 2013 at 18:05
  • @BilltheLizard Isn't there a way for 10K users or moderators to close-vote the questions in this list more efficiently? (I don't exactly know the tools 10K users or moderators have access to)
    – Jocelyn
    Commented May 4, 2013 at 18:27

1 Answer 1


Maybe with some data-queries the low hanging fruits can be picked more easily for deletion. Not that this query is perfect, but it can be a start:

  • I prefer to use this list and go to the last pages to get the questions with the lowest scores.
    – Jocelyn
    Commented May 4, 2013 at 17:36

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