When several tables have a null name, the previously used localIdGetter would make comparison fail. This new version tries to work around this issue by using children (i.e., column) names.
Like the previous localIdGetter, this is still specific to the Relational metamodel, and is still fragile. However, it might be enough for this case.
The best solution I know of would be to leverage trace links (see issue #25). However, this would make it necessary for all submissions to serialize them, which is not currently considered.
When several tables have a null name, the previously used localIdGetter would make comparison fail. This new version tries to work around this issue by using children (i.e., column) names.
Like the previous localIdGetter, this is still specific to the Relational metamodel, and is still fragile. However, it might be enough for this case.
The best solution I know of would be to leverage trace links (see issue #25). However, this would make it necessary for all submissions to serialize them, which is not currently considered.