drakewire Posted August 28, 2007 Share Posted August 28, 2007 I have a minor issue and perhaps I am not looking close enough. I have this issue with a project where the guy installed all of these third party scripts, after examining the core structure of the databases there login systems use the following: Script for email table / user userid username password --------------------- community script table / community_users id user password ---------------------- News table / tBlusers userid username password ----------------------- Bookmarks table / Link_session name pass ------------------------ What would be the easiest way to integrate the login /slash registration systems on all of these different scripts so that I can finish this project quickly.... He doesnt want to integrate just integrate the login/ registration / logout system... But they all seperate databases... I was thinking of using globals since they all use session... and designing a new registration system for all of them, but this would be a pain in the arse since I would have to delete every instance of login data on all of the scripts.... There has to be an easier way.. ? Quote Link to comment Share on other sites More sharing options...
ReDucTor Posted August 28, 2007 Share Posted August 28, 2007 One thing you could do is use sql views to replace the tables, create a single registration, and rest pass. http://dev.mysql.com/doc/refman/5.0/en/create-view.html Quote Link to comment Share on other sites More sharing options...
drakewire Posted August 28, 2007 Author Share Posted August 28, 2007 hmmm yeah I thought of that but that would imply that there is existing data in the tables, to which there is no data currently in the scripts. What I was kind of thinking was since these are third party scripts Ive noticed that almost every table is unique with the exception of the username and pass which is a little different, what I was thinking was just to copy the SQL tables into one master database, but this wont work I dont think. This way you create one registration form with all the data that could be asked in the seperate login forms. Then log outs would fall under the same pretenses... However, since these different scripts are using different registration forms and different logins different log outs this may be a problem... However, I wouldnt have to edit a whole bunch of code since all the tables would be the same.... I.E each of these scripts have a config file for the database, so I can change this into one master database keeping only user and password as the new unique id's that will be added... Hmm? What do you think Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.