Bug #9714
Remove LocalSyncher as it has become dead code
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
History
#1 Updated by Andrei Plugaru over 1 year ago
From Eric in #9701-24:
Please note that LocalSyncher is effectively dead code. We really should remove its use. It is based on the notion that we can have foreign keys between primary tables. We have long since determined that this is not feasible, since there is no referential integrity enforced by the Progress database, so much application code is written that would break referential integrity. This was causing database errors when applied to modern DBMS', so we stopped using it.
Persistence.isForeignKeysEnabled really should return false, or be removed entirely (along with code that depends on it returning true).