DAP Client syncing tables returning "pysqlsync base QueryException": column resource_link_lookup_uuid cannot be cast automatically to type uuid

[ByambaBird]

When we are running our DAP synchronizer python script, we are running into issues going back to Feb 27. This was the last time it ran successfully and we noticed it 2 days ago. When diving into the issue we are finding that several tables now are trying to cast automatically to type uuid. 

How do we fix this?
Should we drop the Tables? If we do will the DAP client actually see it as dropped and re-init the tables?

[LeventeHunyadi]

DAP client library had a release of version 1.1.0 on March 20. Since you mention that you have had the issue going back to February 27, can you double-check if you use the most recent version? There have been some improvements, which might cover the issue you are reporting.

If you decide to drop the table, make sure you use the dropdb command. Otherwise, there are going to be orphaned entries in the DAP client library meta-table (called instructure_dap.table_sync), which tracks replication information, and the client library will continue to believe as if the table were there and won't let you run initdb. After you run dropdb, you can get a full snapshot with initdb, which you can keep up to date with syncdb, as described in detail in the documentation.