We’re releasing DAP CLI version 1.3.1 today to address an issue that affected PostgreSQL users following our recent DAP Query API update. Yesterday, we introduced multiple new enum values across several tables in the DAP Query API, which unfortunately revealed an unforeseen bug when running the syncdb command in DAP CLI.
While our CLI is designed to handle new enums seamlessly, the issue arose when multiple enums were added at once. This only impacted PostgreSQL users attempting to synchronize their databases using the syncdb command. We’re happy to report that this issue has been resolved in version 1.3.1 by updating the required version of pysqlsync to 0.8.1, which now handles such cases correctly.
What’s Changed
- Updated DAP CLI’s dependency on pysqlsync to version 0.8.1, which fixes the issue with syncing PostgreSQL databases when multiple new enums are introduced.
- Added a new test case to our automated testing system to ensure this issue does not recur in future releases.
What You Need to Do
If you are using PostgreSQL with DAP CLI, we strongly recommend updating to version 1.3.1 to ensure smooth syncing of your data.
To update your DAP CLI, run:
pip install -U instructure-dap-client
Or download the package directly from pypi.org.
We apologize for any inconvenience this may have caused and appreciate the feedback from our customers that helped us quickly identify and resolve the problem.
As always, thank you for your continued support!
