When running dap syncdb using our MySQL 5.7 database we get the error shown below for several tables. When dap syncdb is run for the same tables using our development MySQL 8.0 database we do not get...

The issue is related to the handling of utf8 data by our older, MySQL 5.7 database. The issue was resolved by altering the database to use the newer MySQL utf8 character set and collation. The resolut...

Thank you for your quick response. I agree there can be name collisions if loading both namespaces into the same MySQL database. Our school is not using Catalog and an alternative solution, such as re...

We devised a simple workaround to utilize dap 0.3.18 to load our production MySQL 5.7.15 tables. All of our CD2 SQL queries have been tested and deployed into production using the non-prefixed table n...

Would reinitializing the database with 1.0.0 work? What is the expected date of the release containing the fix?

Thank you for your quick response. I agree there can be name collisions if loading both namespaces into the same MySQL database. Our school is not using Catalog and an alternative solution, such as re...

We devised a simple workaround to utilize dap 0.3.18 to load our production MySQL 5.7.15 tables. All of our CD2 SQL queries have been tested and deployed into production using the non-prefixed table n...

Would reinitializing the database with 1.0.0 work? What is the expected date of the release containing the fix?

Replying to my question instructure-dap-client · PyPI

 When running dap syncdb using our MySQL 5.7 database we get the error shown below for several tables. When dap syncdb is run for the same tables using our development MySQL 8.0 database we do not get...