Google SearchEngineUpdater: campaign-level sync (--accounts) updates searchEngineAccounts unnecessarily

On 10/11 at 5:00 PM we ran into performance issues on acctdb05 that caused replication to take much longer than usual.

The below 2 columns store a CSV list of network targets and content targets. If Google returns the targets in a different order, it results in DB updates even though the targets are still the same.

networkType

contentType

To fix this, we can stop using these columns, and replace all read/write references with the new TargetingDAO class. The TargetingDAO class makes these columns unnecessary, because all of the information is stored in the targeting database and retrieved using the targetingDAO. See YahooAPISearchEngine.ListingChunk.getListings() for an example usage of reading targets from the TargetingDAO.

To view this happening, run the following query:

mysql> select * from logging.searchEngineAccountChanges where `column` in ('networkType') and searchEngineAccountID=43 and changeTime > '2010-04-10';

-------------------------------------------------------------------------------------------------------------------------------

-------------------------------------------------------------------------------------------------------------------------------

-------------------------------------------------------------------------------------------------------------------------------

17 rows in set (0.03 sec)