TABL - "Delete and recreate local object" will lead to data loss

[larshp]

When pulling a transparent TABL, abapGit determined to "Delete and recreate local object", which will lead to data loss. The table exists locally and remotely.

As usual, the status information is wrong, there is not enough information in abapGit to determine if "added locally or deleted remotely"

we need to remove/revamp the status functionality so its correct in all cases

the possible cases are:
a. exists locally only
b. exists remotely only
c. exits in both, differences
d. exists in both, identical

might also be in connection with a package move

[mbtools]

Options:

1. enhance checksums to work by branch/tag/remote
2. remove checksum feature completely (it's not needed for the listed cases)

Without checksums, we won't be able to tell which side was changed. So "add" or "delete" status won't be possible, which has implications to pull and stage dialogs. Also "diff" colors (green vs red) are not clearly defined.

However, I don't see how checksums are related to the "TABL re-create" problem. If abapGit actually showed "Delete and recreate local object" then it's a UI issue to present this more clearly as a warning that might require extra confirmation.

[larshp]

when manually moving local object to the right package, the status changes to "Overwrite local object" instead of "Delete and recreate local object"