How dangerous is addressing non-vbulletin tables in vbulletin?
 

Hello. I have a site which uses a custom database to store reviews. I don't believe any of the variables of that program overlap vbulletin's. I would like to write a fairly extensive hack to replace the custom code that addresses those tables.

How dangerous is this to the two databases (I'll be doing the tests on a local machine first before doing this on the server) or can it even work?

Bump

You're rather vague when you say "addresses those tables."

Do you simply mean you wish to combine them?

It shouldn't be a problem, as long as there are no duplicate table names.

Yeah, combine them I guess - I can alter the table names if necessary. The two databases are on the same server so I don't *think* there are any duplicate names.

If they are two separate databases, then there is no problem. If they are just different tables in vB's database, then it would not be advisable.

Ok, well I'm getting in so deep now it's high time I read the :ahem: manual for MySQL and PHP. I'm wanting to do some fairly complicated functionality hacks, some of which I don't necessarily want to share since they've be exclusive to the board I work on.