kwill, I have no problem whatsoever with testing software, by the way i recommend it by the dozen. The problem is there was not enough testing because obviosly nobody checked to see if SQLWB ran in 14.10. Ok, it happens, it was identified and a fix was provided for 6.2.4 which obviously wasn't tested enough, resulting in the bug being there after the fix. Guess what? I had 6.2.3 and never warned me of new version, even when I deliberately checked for new versions. I discovered 6.2.4 was launched because went to the website looking for the release date. So, updates are also not working right. I came to this forum and a fix was provided via the utopic prerelease and guess what? Didnt do jack to fix it.
I work as a developer for a living, and you can be sure that the products I put out there for my paying customers DO HAVE bugs, but I try to ease their pain with the software by not introducing new roadblocks. I would never ever suggest that they download my source code and build tools and compile the fix themselves. Thats my job. I use and love SQLWB to do my work and right now I'm unable to use it because of this bug, and every effort to fix it was unsucessful, and that's why I vented before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376154 Title: data grid not displaying resultset is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-workbench/+bug/1376154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
