[Attachment(s) from Scott Sanders included below]
I viewed the data of a table in an existing MySQL DB where mdate looks like11/10/2009 9:50:49 AM.
I get the same issue here - but it only happends where date fields have null values.Previous version of Toad had no trouble with this, though; I keep 4.6 around for this reason. 4.6 just seems to substitute 1/1/0001 to display null value dates in the grid.
I had my PC re-masterized by IT services and had the same issue after installing the new version of Toad for MySQL. I confirm that apparently, the tool is sticking much more with the table definition which makes this kind of errors appear when you have "NOT NULL" columns with "NULL" values.I truncated my table, changed the definition of all my dates where I know there could have null dates and re-imported the data again.Since then, no more issues with Toad!Also, I'd like to add that now the "Import" tool is working just fine (with a huge CSV file of 150Mb) while it was always crashing the software at the end with the previous version ;)Hoping this will help somebody...Tanhys
Any news on this one yet?I still have to use 4.6 next to 5.0Awfully quiet in this group lately, btw.
I actually was using the Beta version (6.0) because of this and was very happy. But now after using the beta for so long it says something to the effect the 'Beta period is expired' and it sends me to download 5.0 again. I have never seen a beta that expired ... When is this beta going to be GA so I don't have to deal with 5.0 anymore (too many bugs)
Actually the latest beta does not really solve the problem -- it just moves all these errors to the hidden output tab at the bottom.My guess is that it has issues with blank values for dates -- and I read somewhere that putting Allow Zero Datetime=true in the connection string may fix it.
Yes, that is what we are doing however since this does actually change the value you see in the grid a warning that this has happened whenever we read one of these values (That is what you are seeing in the output tab) so this is the expected behavior.
It changes the display of the value -- to blank, like other valid cells -- and does not indicate a problem, nor tries to fix it, nor shows in the output which cells or rows these may be, just their column names.Contrarily, SQuirreL at least shows these cells as , but it does not let me fix them -- so presently, I am finding all of these cells in SQuirreL, finding them again in Toad by ID, editing a random cell in that row with Toad, and editing it back with Toad, so the cells are just nullified, as they are causing issues elsewhere.
Unfortunately the component we use to access MySQL does not allow for this.It's easy to find them with a query though:select * from table where datecolumn = '0000-00-00 00:00:00'