title: MySQL Connector for .NET - Is it REALLY mature?
body: <p>After spending a miserable month with MySQL/.NET/EntityFramework, my findings:</p>
  
  <p>Support for Entity Framework is VERY primitive, please use it for student-subjects type of database. Kindly do not consider it using for serious development as they ARE STILL unable to sort out VERY BASIC things like:</p>
  
  <ul>
  <li>it DOES NOT support unsigned stuff</li>
  <li>it DOES NOT support unsigned columns as FK; if you try, it gives you a beautiful exception; "The specified value is not an instance of a valid constant type\r\nParameter name: value" [<a href="http://bugs.mysql.com/bug.php?id=44801]" rel="nofollow noreferrer">http://bugs.mysql.com/bug.php?id=44801]</a></li>
  <li>blob cannot store more then few KB;</li>
  <li>cannot compare null object with a column with a LEGAL null value [<a href="http://bugs.mysql.com/bug.php?id=49936]" rel="nofollow noreferrer">http://bugs.mysql.com/bug.php?id=49936]</a></li>
  <li>they are unable to write VERY PRIMITIVE check to return date as null if value in column is 0000-00-00 00:00:00</li>
  <li>if you use Visual Studio; sorry; mysql/sun guys hate Microsoft, they will NOT LET you import more then two or three tables (for Micky Mouse type of tables, they allow five; but thats it) - if you try, it will throw TIME OUT error on your face ... unless you are smart enough to change the connection time in connection string</li>
  </ul>
  
  <p><strong>Anyone who would like to add in above list?</strong> </p>
  
  <p>WISH I would have seen a list like this before I selected MySQL :(</p>