RhodeCode CE/EE

This looks like it is built as a feature, not sure if it was by design or on accident. However, it is in-fact a huge issue with the workflow of RhodeCode.
If I fork a repository, make some changes then open a pull request and ultimately get that pull request to be accepted and merged into the upstream repository, I would expect that no matter what happens to my fork, the pull request will continue to be accessible for historical reference of that merge.
However, if on completion of the merge I decide to delete my fork, all data pertaining to that fork is also removed from the database. This includes the entries in the pull_requests and changeset_comments tables. It effectively blows away all historical data for that merge. That is terrible! If anything the entries in the database should be marked as "deleted" rather than just a straight up row delete. I was pretty shocked to see this.