Sja Inserts And Then Deletes Rows

[zgolus]

Hi!

I've noticed strange behavior of sja on linux; I've got two tables to sync and everything goes well the rows from source table are being inserted into target one but in the final step sja deletes them again; structers are identical and both tables have PK on auto-incremented first column and two indexes for faster selecting on second and forth column; the result of syncing looks like this:

Code:

SQLyog Job Agent Version 5.0
Copyright (c) Webyog Softworks Pvt. Ltd.. All Rights Reserved.

Sync started at Wed Feb 22 18:06:23 2006

Table                      SrcRows  TgtRows  Inserted  Updated  Deleted
=========================  =======  =======  ========  =======  =======
`lem_pl`                   4156892  3797477    359415        0   359415

Total time taken – 2179 sec(s)

the exect structure of lem_pl table is:

Code:

CREATE TABLE `lem_pl` (
 `lem_id` int(10) unsigned NOT NULL auto_increment,
 `lem` varchar(100) collate utf8_polish_ci default NULL,
 `code` varchar(10) collate utf8_polish_ci default NULL,
 `parent` int(10) unsigned default NULL,
 `word_id` int(10) unsigned default NULL,
 PRIMARY KEY  (`lem_id`),
 KEY `lem` (`lem`),
 KEY `parent` (`parent`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_polish_ci AUTO_INCREMENT=5341204;

have you got any idea why it happens?

[peterlaursen]

Oh .. those details .. hard to remember.

It is only the PK that matters. the 'ordinary' indexes don't play a role.

I am always sure that this is an issue that has been fixed. But I simply cannot recall details right now. I think a checksums issue with 'unsigned'

Latest verison is 5.02. Filename sja502.tar.gz. Uploaded to server 12-12-2005.

Would you mind trying latest build if you don't have it

[peterlaursen]

Also remember to check for next version soon.

There is an issue with PKs involving timestamps that has been solved.

[zgolus]

first of all – thanks for your reply!

You suggested that the issue might have something to do with PKs being unsigned, so I've changed it to default value, but that also didn't solve the problem; during last sync job it went like that:

Code:

Sync started at Sun Feb 26 23:10:00 2006

Table                      SrcRows  TgtRows  Inserted  Updated  Deleted
=========================  =======  =======  ========  =======  =======
`lem_pl`                   4159351  4156892    754907     2200  1554267

Total time taken – 4189 sec(s)

any more ideas?

and btw – I'm using the latest SJA

[Ritesh]

If the data is not confidential, then can you send me a dump of the data?

I cannot correctly comment on the issue without looking at the data.

[Author]

Posts