Import to new Repository - DANGER!

DVLS 4.5.0.0
RDM 12.5.4.0

I made a mistake or kind of found a potentiel bug with the Repository feature.
We are currently only using the Default repository (RepositoryID=NULL)


I wanted to make a copy of a root level folder into a new repository, but without credentials.


1. I created a new Repository and a DataSource for it.
2. I then exported the root level folder and all of its entries, without including credentials using "Export Group (.rdm)..."

3. I then accessed the datasource with my new empty repository and imported the .rdm file

4. Now all entries are inside the new repository, but also my credentials without usernames and passwords.
5. But now my Default repository was missing this exact root level folder and all of its entries.
6. I resolved it by manual SQL queries using the ConnectionHistory table inside the database, to recover all the affected entries in the Connections table. Relying on the highest "ID" inside ConnectionHistory, for all ConnectionIDs currently inside the new Repository.

My concerns are, that I did not receive any warnings in step number 3, while doing the import, which could have warned me about conflicting Connection IDs.

PS. I was currently without Full log backup of the database, only a "copy-only" backup from last night was available. (due to a database move yesterday)
Otherwise I would have just used Point in time restore in SQL to resolve the problem.

Regards

Michael