| Summary |
0004970: Auto resolve missing foreign key with load only or extract only node |
|
| Revision |
2021-04-30 16:51 by elong |
|
| Description |
The automatic resolution of missing foreign key conflicts is running on the default platform instead of the platform of the target database. For example, a load-only node is using the built-in H2 database to detect the SQL code of the conflict, and an extract-only node is using the built-in H2 database to run SQL to retrieve missing foreign key. |
|
| Revision |
2021-04-28 18:31 by elong |
|
| Description |
The automatic resolution of conflicts is running on the default platform instead of the platform of the target database. For example, a load-only node for MySQL is using the built-in H2 database to detect the SQL code of the conflict and run SQL to auto correct instead of using MySQL. |