Comment 4 for bug 660358

I see, that makes sense. In which case, providing a way to access branches via an immutable ID (be it primary key or some surrogate ID) sounds like an interesting possibility for fixing the "rename breaks stacking" issue without needing to run an O(number of stacked branches) job when a rename is performed.