dap-client v1.0.0 failing when attempting execute mysql_0_to_1.sql

MarkAgar
Community Member

Hi,

After updating the dap-client to v1.0.0 we appear to be experiencing an issue when attempting a syncdb on tables against the pre 1.0.0 syncs that were successful against our on site MySQL database.

When we attempt a syncdb on the accounts table i.e. 

dap --loglevel debug --logfile dap.log syncdb --namespace canvas --table accounts --connection-string mysql://my_connection_string@my_cd2_db_server/CanvasData2

In the dap.log we are seeing ...

2024-03-05 08:50:50,504 - DEBUG - Checking connection to mysql://my_connection_string@my_cd2_db_server/CanvasData2 (abstract_db_command.py:14)
2024-03-05 08:50:50,534 - DEBUG - Client region: eu-west-1 (api.py:114)
2024-03-05 08:50:50,534 - DEBUG - synchronizing table: canvas.accounts (sql.py:61)
2024-03-05 08:50:50,674 - DEBUG - No version records found in "instructure_dap__database_version" (db_version_upgrader.py:67)
2024-03-05 08:50:50,674 - DEBUG - Current version: 0; Latest version: 1 (db_version_upgrader.py:40)
2024-03-05 08:50:50,674 - DEBUG - Upgrading database (db_version_upgrader.py:45)
2024-03-05 08:50:50,674 - DEBUG - Running upgrade scripts from version 0 to 1 (db_version_upgrader.py:81)
2024-03-05 08:50:50,684 - DEBUG - Upgrading from version 0 to 1 (db_version_upgrader.py:85)
2024-03-05 08:50:50,684 - DEBUG - Running upgrade script: C:\Program Files\Python\Lib\site-packages\dap\version_upgrade\mysql_0_to_1.sql (db_version_upgrader.py:89)
2024-03-05 08:50:50,714 - DEBUG - Executing SQL: DROP PROCEDURE IF EXISTS InsertMetaIfTableExists;

Looks like it can't do the upgrade sql query?

Thanks in advance for any pointers.

0 Likes
Users who also had this question