TIMESTAMP format not being accepted from dump

[Padmavani Greenleaf]

Hi, I'm sort of newish to SQL, but have been working with it from time to time over the last three years, using a MySQL server installed on a mac.

I'm now using a new mac and therefore an up to date installation of MySQL community server and desktop manager (downloaded and installed today).

The data dump I've been working with that comes from a website I help manage the data from imports fine into an online SQL server/manager I've been using for the last year (when I didn't have access to a local engine), but on this version of the engine I'm getting import errors from the dump query data when it gets to TIMESTAMP values.

The column definition is:

last_success_date timestamp DEFAULT '0000-00-00 00:00:00'

and the query falls over at the default value (and if I remove that from the column definition, the query falls over at any subsequent instance of a value that matches that one in the definition).

Any suggestions as to why this isn't working here but does on the non-local engine would be really welcome. I've already got a find/replace script that tidies up the data before import, so if there's something I can tweak globally that'll make this work, that would be great. For the purposes of using this data dump, we literally just need that value to show up as zero or some suitably out-of-range date like 01-01-1970 so it's obvious it's been filled in by the database.