[MySQL 4.1.7 -> 4.0.21-log] Timestamp trouble

[Erik]

Hi,

After I've came to the conclusion that syncing mysql 3.23 to 4.x didn't work, we (me and my customer) bought SQLYog. Now we seem to have a similar problem, which doesn't exist when syncing 4.1.7 <-> 4.1.7.

Here are some examples:

Code:

Definition mismatch for 'timestamp' column in '`boek_antiek`' table
Definition mismatch for 'timestamp' column in '`boek_nieuw`' table
Definition mismatch for 'timestamp' column in '`landkaart`' table
Definition mismatch for 'timestamp' column in '`prent`' table

I suspect this has something to do with the different timestamp types. On 4.0.21 the timestamp colums are of type `timestamp(14)' – which i cannot change. On the 4.1.7 machine these are `timestamp' colums.

Do you have any idea what I can do to eliminate this problem? I cannot upgrade the 4.0.21 mysql server – this is the webserver.

Thanks in advance for any help you can give me.

[Ritesh]

We are working on this issue.

Your idea about the problem with 'timestamp' is correct 😀

Quote:

After I've came to the conclusion that syncing mysql 3.23 to 4.x didn't work

Can you tell me the problem you are facing?

[Erik]

Ok I'll try 🙂

I've got two setups – one at home for development, and one 'live' setup at my customer's office.

At home I had a unix/freebsd server with mysql 3.23 and a windows client with mysql 3.23. Everything worked fine with no problems at all. When I tried the exact same db structures for client and server at my customer's office (client = 3.23 and server = 4.0.21) synchronising didn't work. I got a lot of errors like:

Code:

Error No. 1062
Duplicate entry '2' for key 1
Error No. 1062
Duplicate entry '1012' for key 1

I figured it had something to do with the versions because that was the only difference between development and live setup. I upgraded the development setup to 4.1.7 (which implies upgrading to the new sqlyog which we did). Everything works fine again in there (client = 4.1.7, server = 4.1.7) – but not in the 'live' setup (client = 4.1.7, server = 4.0.21).

I can't do anything about 4.0.21 – it's running at an ISP.

The odd thing about this is I'm not even synchronising this timestamp column! It's just workaround for MS Access at the client machines.

That's about the whole story (-:

Maybe using one of the alternative synchronising methods (http or ssh tunnel) is a solution to avoid this problem?

[Ritesh]

I think we had fixed a similar bug in SJA 4.0.

Are you still facing problems in the 'live' setup (client = 4.1.7, server = 4.0.21) with the latest release?

[Erik]

Ritesh wrote on Nov 25 2004, 11:39 AM:

Are you still facing problems in the 'live' setup (client = 4.1.7, server = 4.0.21) with the latest release?

Yes – with the timestamps definition mismatch.

[edit] Congratulations BTW 😉 [/edit]

[Ritesh]

Erik wrote on Nov 25 2004, 11:43 AM:

Ritesh wrote on Nov 25 2004, 11:39 AM:

Congratulations BTW 😉

:huh: :huh:

[Erik]

1 member is celebrating his/her birthday today

>Ritesh (21)

🙂

[Ritesh]

He He.

Thank you 😀

[Erik]

I hope you can help me with this timestamp problem?

I really want to get the client-server setup ready in November.

[Erik]

The problem resolved itself: The ISP upgraded to 4.1.7 😉

[Ritesh]

That is a wonderful news. I hope things are working as expected 🙂

[Author]

Posts