title: MySQL Workbench - how to diagnose query failure problems
body: <p>I have loaded MySQL and MySQL workbench on my PC, and am using it to build up my SQL skills, accessing only data stored on and served by the PC itself.</p>
  
  <p>When a query fails the only message I get is one telling me it failed because of an error. </p>
  
  <p>Is there any way to get more helpful information about what problem the software detected that caused it to raise the error message?</p>
  
  <p>I am using WorkBench 6.0 on linux mint Rebecca. I am also using it on the same PC (dual-boot) on windows 7, although I don't know the windows WorkBench version right now because I'm writing this from linux. In both cases no info is provided about why the query failed. In WorkBench 6.0 on linux all I get is a 'Query Interrupted' message. On windows I just get a white cross on a red circle telling me there's an error and that I need to correct my code.</p>
  
  <p>If the best solution is to use something other than WorkBench I'm quite open to that. I'm starting to wonder whether WorkBench is not the best tool for this type of activity aimed at developing sql query skills. The docn spends a lot of time talking about forward and reverse engineering and models, and I think I've got the general idea of what that is, but all I want to do is read in tables from csv files, manipulate and analyse them, then write out some result tables. I wanted a GUI that would also let me browse the tables, and highlight syntax  errors in the code editing window, and thought that WorkBench would be the tool to do that, but it looks like it might be aimed at doing much more than that, and may be an unnecessarily complex environment for what I'm trying to do.</p>
  
  <p>Thank you</p>