Critical error report! resulting in data loss

[gabriel.duro.s]

@stefano.menci

I would add to what @gabriel.duro.s says that checking out a commit without a branch will allow you to see that commit in read only mode.

If you want to change something you can create a new branch on that commit, then check it out, and you will be able to make changes.

Yes, you’re right. Thank you for correcting/completing that, specially about the difference between checking out the commit rather than creating a new branch from that commit.

@mideruit

I can’t imagine user unfriendly loops being part of the intended behaviour

I kinda agree about that “loop”. I think it protects the dev most of the time by preventing a unintended change to the database just by viewing an old commit.

@mideruit

Also the “Schema mismatch” loop is also very user unfriendly.

@stefano.menci

I agree that the UI should make it more difficult to change the database.

However I also agree that the diff page for schemas (and the UI for merging conflits) is somewhat not user-friendly. I think there’s already a Feature Request for that, if I’m not mistaken.