0011386: one mantis with multiple database to separate physically project

ID	Project	Category	View Status	Date Submitted	Last Update
0011386	mantisbt	feature	public	2010-01-12 08:46	2010-01-14 08:46

Reporter	ccheret	Assigned To
Priority	normal	Severity	feature	Reproducibility	N/A
Status	new	Resolution	open
Product Version	1.1.8

Summary	0011386: one mantis with multiple database to separate physically project
Description	Do you plan to propose this option: One mantisbt with multiple database to separate physically project data. In some case, it's a requirement . Rgds. CC.
Tags	No tags attached.

ccheret 2010-01-12 12:21 reporter ~0024133	When creating a new project, it will be usefull to be able to have choice to use the Mantis global database or a project dedicated database. C. C.

dhx 2010-01-14 08:46 reporter ~0024150	I can see the benefit in trying to separate out database storage on a per-project basis. For instance, users, bugs, configuration, etc is stored in a different database for each project. It'd still be required to have a database containing global data (across all projects). I guess the main problem is managing conflicts between automatic indexing of users (user1, user2... user10...), bugs, attachments, bugnotes, etc. If you wanted to export a project from one Mantis installation to another - how would you manage the conflict possible between overlapping bug IDs? The changes you ask for here essentially force us to have numbering done on a per-project basis. Or not use numbering at all - and use unique randomly generated hashes instead. This is a huge architectural change that would require Mantis to essentially be rewritten from scratch.