Re: perl DBI statement

"If you use the IGNORE keyword, errors that occur while executing the INSERT statement are ignored."

It would be interesting to see the results if "IGNORE" were removed.

If it were me, I would also make sure that the insert loop is actually running, to make sure "WHERE entry_time >= $time" was returning the rows i thought it should.

Comment on Re: perl DBI statement

Replies are listed 'Best First'.
Re^2: perl DBI statement by cbtshare (Monk) on Dec 04, 2016 at 12:54 UTC
Yes, I have tried that, the issue i run into is DBD::mysql::st execute failed: Duplicate entry '00000510011339735_1015422747869973' for key 'PRIMARY' at /home/rdscopy.pl line 104. DBD::mysql::st execute failed: Duplicate entry '00000510011339735_1015422747869973' for key 'PRIMARY' at /home/rdscopy.pl line 104. Line 104 is: $sth_insert->execute(@insert) or die $sth_insert->errstr;	[reply]
Re^3: perl DBI statement by poj (Abbot) on Dec 04, 2016 at 13:32 UTC
You can't insert a record with the same primary key as an existing record. If the destination table is empty then it looks like the source table does not have the same primary key contraint as the destination table. poj	[reply]
Re^4: perl DBI statement by cbtshare (Monk) on Dec 04, 2016 at 13:44 UTC
yes, the destination table is truncated.So the issue is the source table? how would I solve this issue?	[reply]
Re^5: perl DBI statement by huck (Prior) on Dec 04, 2016 at 15:42 UTC
Re^6: perl DBI statement by cbtshare (Monk) on Dec 04, 2016 at 19:18 UTC
Some notes below your chosen depth have not been shown here