You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The db_sync module does not handle well the scenario where the source table is empty, and in most cases will result in a confusing error being raised (destination table does not exist). This is due to trying to run a row count at the end of the sync. Even if running an incremental sync with verify_row_count explicitly set to false, if the source table is empty, the sync reverts to a full sync and does not pass along the verify_row_count flag.
Detailed Description
To Reproduce
Your Environment
Version of Parsons used (if you know):
Environment name and version (e.g. Chrome 39, node.js 5.4):
Operating System and version (desktop or mobile):
Additional Context
Add any other context about the problem here.
Priority
Please indicate whether fixing this bug is high, medium, or low priority for you. If the issue is time-sensitive for you, please let us know when you need it addressed by.
The text was updated successfully, but these errors were encountered:
The db_sync module does not handle well the scenario where the source table is empty, and in most cases will result in a confusing error being raised (destination table does not exist). This is due to trying to run a row count at the end of the sync. Even if running an incremental sync with verify_row_count explicitly set to false, if the source table is empty, the sync reverts to a full sync and does not pass along the verify_row_count flag.
Detailed Description
To Reproduce
Your Environment
Additional Context
Add any other context about the problem here.
Priority
Please indicate whether fixing this bug is high, medium, or low priority for you. If the issue is time-sensitive for you, please let us know when you need it addressed by.
The text was updated successfully, but these errors were encountered: