New profile is allowed to use an already existing database (of another profile)

[aiida-bot]

Originally reported by: Spyros Zoupanos (Bitbucket: szoup, GitHub: szoupanos)

---

Please also see if an already existing repository is possible to be used.

In general each profile should have its own database and repository.

Best,
Spyros

---

• Bitbucket: https://bitbucket.org/aiida_team/aiida_core/issue/168

[aiida-bot]

Original comment by Giovanni Pizzi (Bitbucket: pizzi, GitHub: giovannipizzi):

---

I think this in general should not happen, but I don't know if it's easy to avoid that two people use the same DB or repo (and probably it's ok to let them do it). Maybe the only check can be with existing DBs and repos in the same config.json. I suggest to change verdi install (and the docs) along the line of what I did (for basically the same reason) earlier today for the repo: now, the default repo name suggested in the installation phase is not only ~/.aiida/repository but ~/.aiida/repository-{PROFILENAME}.

I suggest to change the default database name from aiidadb to aiidadb_{USERNAME}_{PROFILENAME} (in all three supported cases with django) [and maybe the default DB username to the linux username]. Underscores should be supported by all backends, right? Also the docs on how to create a new DB should be updated so that users start from the very beginning creating a DB with the right name (e.g. aiidadb_{USERNAME}_default if they don't provide a profile name).

[giovannipizzi]

I think the default name changed (but probably not as suggested here - @DropD can you confirm?

Also, the new work in the object store will take care of making sure that the file storage and the DB match.

[giovannipizzi]

Actually, this is a duplicate of #182 - after checking/fixing that the default name contains the linux username, I would close this issue.

[DropD]

default name contains getpass.getuser()