When an SQL error occurs, they are not handled really well. One must look in the
logs to actually see them, and sometimes the sync tool tries to continue, even
though all SQL errors are fatal.
Fixed in CVS... no QA as of yet...
o SQLError, SQLSchemaError, and SQLCommunicationError errors are caught.
o assumption that all such errors are fatal is made.
Never QA'ed; reopening... and tracking
*** This bug has been marked as a duplicate of 75903 ***