Problem dumping database to another server

  • setalosas

    (@setalosas)


    21 years, 2 months ago

    I moved my site to another server and tried to use mascon (windows client) to dump the old database onto the new server (both linux, old is mysql 3.23, new is mysql 4).

    During the dump (using ‘dump directly to server’ option) mascon gave several error messages like ‘1048 – column “pinged” cannot be null’. (Actually this was repeated several (7-8) times, but with different field names of different tables).

    I tried to change each problematic field (on the source server) to set ‘allow null’, and retry, eventually the dump was successful! But I am a bit worried, why this error came up, and if my solution could make any trouble for me in the future?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Mark (podz)

    (@podz)

    21 years, 2 months ago

    Not heard of mascon.. and by the sounds of it I’ll not be seeking it out.
    Do you still have the original database intact, and if so, what sort of access do you have to that ?

    Thread Starter setalosas

    (@setalosas)

    21 years, 2 months ago

    mascon is a basic mysql admin client for windows, I use it for years for dumping and browsing different databases, I find it quite handy.

    I have shell access to both the source and destination computers, and I could use mysql directly too. I use mascon because it’s easy to establish a dump, I don’t have to remember any syntax stuff. Do you think this problem is related to mascon and not the database itself?

    The current database is not critical for me (it seems it works fine now in the new place), but in the future I’ll have to move another WordPresss blogs from one server to another, so I’d like to see what was the problem here…

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Problem dumping database to another server’ is closed to new replies.