Re: Merging mantis databases.. down the line.

On 04/22/2009 05:20 AM, Jon Hardcastle wrote:
> Hi,
>
> We have adopted mantis as the issue tracker of choice for our development department, and it is mainly going great guns. Our client team department would also like to use it as a kind of help-desk system too.
>
> Problem is both areas have made changes that for ease of use (use to project properties not being inherited) are best done 'globally' to save me having to migrate the project setting every time they create a new area in the system.
>
> I would love for everyone to use 1 instance of Mantis as it makes telling people where to go and how to log in nice and easy - but i just dont see how it is possible without there being a massive and quite regular admin overhead.
>
> I know that inheritance is on the cards - but that it will be a while before it supports all properties and does so without issue. So what i want to know is can i run the 2 areas as separate installs. The first area can have the first 1,000,000 issue id's and the section from 1,000,001. Then when Mantis has the support for inheritance bring the 2 together.. and kick off all the new issues from 3,000,000 to make sure there is no tripping over of issues.
>
> Is this something that is possible?

Yes, it's possible; just alter the bug_table after creation to set it's 
auto_increment (or equivalent) to start at the number in question.

However, I think it might be "better" if you had the two separate 
installations, each with their own global customizations, still running 
out of the same database, assuming that there's no conflict for things 
like statuses, etc.  The only "trouble" with that setup is that you then 
have the potential to work with the wrong projects from the wrong 
installation, although since I'm not sure what type of customizations 
you're discussing, I don't know what the implications of that would be. 
  You could however attach a bit of code to bottom or each site's 
core.php (or somewhere else) that would redirect the user if they 
started to work on the wrong project.

Anyways, those are just some ideas, maybe you can run with them. :)

Cheers

-- 
John Reese
LeetCode.net

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p