Log in

View Full Version : Sharing some user account details on concurrent installs

Boards.ie
05-12-2008, 03:29 PM
Hi,

I'm migrating one of our systems from Photopost classifieds to vBulletin for a variety of reasons. We already run a large vBulletin-based site (not heavily modified) and would like to share the profile (username/password/email etc) details of the current vBulletin site with the new one (as the Photopost site is a "subsite" of the primary vBulletin site and already does this).

I'd like to know if there is a relatively simple way of sharing these details (as opposed to copying the details on a cron or something, not feasible with the size of the database). I would like to avoid having to modify the vBulletin codebase manually (it would suit me perfectly if there was a mod for this, but I suspect it is rather too niche).

Perhaps this can be done by symlinking MySQL data tables; could you advise on the best course of action? I would prefer if it was possible to specify by database/table in a config file for the sake of portability.

Many thanks for any assistance.
Dismounted
05-13-2008, 07:29 AM
<a href="https://vborg.vbsupport.ru/showpost.php?p=1479822&postcount=3" target="_blank">https://vborg.vbsupport.ru/showp...22&postcount=3</a>
Boards.ie
05-13-2008, 09:20 AM
Excellent stuff, thanks.

--------------- Added 1210691981 at 1210691981 ---------------

Haven't had much need to touch on VIEWs since college, but it looks like this won't really do the trick.

The view definition is ?frozen? at creation time, so changes to the underlying tables afterward do not affect the view definition. For example, if a view is defined as SELECT * on a table, new columns added to the table later do not become part of the view.

This is not really an ideal solution as it is essentially the same as simply copying the tables, but in an unalterable state. Not necessarily a problem... until the user changes their username/password/email.

Still, it might be easier to have the primary site update the relevant view for the subsite than it would be to have the subsite pull the information from the primary db.