Looks like they still haven't addressed the issues that make toad completely unusable such as errors when viewing table data. Until they fixed these issues I'm sticking to the v4.6. They can't even have the support message link button when an error does arise to go to a valid email address!
Come on toad developers, you used to be cool, what happened?
Re: Toad for MySQL Beta 220.127.116.113 released
Feb 25, 2011 2:12 PM
in response to: Mike The KID
I think he is just trolling. I have several tables with
" MySql.Data.Types.MySqlConversionException Unable to convert MySQL date/time value to System.DateTime Stack Trace: at MySql.Data.Types.MySqlDateTime.GetDateTime() at MySql.Data.MySqlClient.MySqlDataReader.GetValue(Int32 i) at Quest.Toad.Db.Connection.ReadRow(IDataReader reader, FastTable datatable, FastReadOptions options, PrePostProcessHandler prePostProcessHandler) at Quest.Toad.Db.ToadDataAdapter.InternalReadBackground() "
errors displayed in 18.104.22.1685. This error is mostly due to invalid dates such as '0000-00-00 00:00:00', '1000-00-00 00:00:00'......
The issue is 100% resolved in version 22.214.171.1244. I am able to view all data on all tables without error. Invalid dates, which there are a lot of in a lot of different ways, display as an empty cell. This is my expected behavior. Others may want to see a string representation of the date or something else. Potato potato. You have a visual indication that the date is crap and not null. Maybe devs could learn to not make up days to make a column not null. Just use null.
Toad for MySQL version 126.96.36.1994 IMHO behaves as expected for make believe dates.