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
* Fix for double brackets
Fixes the issues related to brackets #24
* Run all those constraints
Fixes the issue #31, This prevents from the program to fail when it has issue running constraint related queries.
If there is a error executing a query to fix the constraint, throw the error on the screen and continue till the end.
At the end the user can manually fix anything if there is any issue.
* Bump the version number
Copy file name to clipboardExpand all lines: README.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,10 +130,11 @@ For more examples how to use the tool, please check out the [wiki](https://githu
130
130
131
131
# Known Issues
132
132
133
-
1. If you have a composite unique index where one column is part of foreign key column then there are chances the constraint creation would fail.
134
-
2. Fixing CHECK constraints isn't supported due to complexity, so recreating check constraints would fail, use `custom` subcommand to control the data being inserted
135
-
3. On Greenplum Database partition tables are not supported (due to check constraint issues defined above), so use the `custom` sub command to define the data to be inserted to the column with check constraints
136
-
4. Custom data types are not supported, use `custom` sub command to control the data for that custom data types
133
+
1. We do struggle when recreating constraints, even though we do try to fix the primary key , foreign key, unique key. So there is no guarantee that the tool will fix all the constraints and manual intervention is needed in some cases.
134
+
2. If you have a composite unique index where one column is part of foreign key column then there are chances the constraint creation would fail.
135
+
3. Fixing CHECK constraints isn't supported due to complexity, so recreating check constraints would fail, use `custom` subcommand to control the data being inserted
136
+
4. On Greenplum Database partition tables are not supported (due to check constraint issues defined above), so use the `custom` sub command to define the data to be inserted to the column with check constraints
137
+
5. Custom data types are not supported, use `custom` sub command to control the data for that custom data types
0 commit comments