question regarding good practice for potential integration
 

Before install vbulletin I was wondering about what's a good rule on setting up SQL for potential integration in the future.

Should I create a separate SQL database for each script? For example vbulletin, RSS feed, and ecommerce have there on SQL database? Or put them in the same database with a prefix to distinguish which is which.

I notice you can set a cookie prefix, should each script have its own prefix or one for all would work?

Thank you in advance for your input.

It depends on the size but I normally just use a different prefix for scripts unless very large and in that case I would use a separate database.

I am not sure what scripts your are going to use that require a cookie prefix but if they are going to allow members log in then they should use the same.

I do not imagine getting huge, but i do want to plan for the future. If i were to make different databases how hard would it be to integrate them? by integrate i meant to use the same login / information.

Im not sure about the cookies. I know vbulleti allows you to create a prefix, but tiny rss doesn't. haven't looked into an ecommerce yet, but would that be a problem what some you can set a prefix with others you cannot?

I am a little confused as to what you are trying to do. If you could be more specific as to scripts I may be able to help more.

Sorry, let me try my best. I want to make it possible for users to be able to log into each script using the same login information, so they only have to register once.

Should I create separate databases for each script? One for Vbulletin, one for Tiny Tiny RSS, and one for wordpress.

Or

Create one database and have each script use its own prefix?

You do not need an rss script with Vbulletin really. It has one built in.

Are you integrating WordPress into Vbulletin? If so I would keep them on the same database with different prefix. otherwise I would use a separate database with a separate database username and password.