2. PHPRunner General questions
  3. I'm having trouble getting started
This topic is locked

I'm having trouble getting started

 		9/29/2010 11:48:46 AM
PHPRunner General questions
K
 karmacomposer author

My client wants to have applicants fill out a large form and THEN approve them with a username and password so that they can fill out even more information. The diagram of the database is massive and will need at least four or five large tables to later be searched by employers. It gets more involved because recruiters need to also login and see their applicants only, while other applicants have no recruiter. Finally, once someone is placed in a job, they need to be moved to another database so that employers can see their employees hired via this database/website.
I assume I should keep all tables within one mysql database. Is it safe to assume you cannot access data/search between different databases?
I created a beginning database for them using another tool, but they want a LOT more customization than that software could give. Hence why I will be purchasing phprunner. I can use the other program to create the database tables and phprunner for everything else.
I am not new to databases having created Access databases before, but I am a bit new to sql databases (using mysql).
Any help or guidance would be appreciated.
Mike
Sergey Kornilov admin 9/29/2010

You won't gain any benefits splitting data into several databases. Keep everything in one database.
K
 		karmacomposer author 9/29/2010



You won't gain any benefits splitting data into several databases. Keep everything in one database.


OK. I have talked with the client and have a much firmer grasp of the project. It looks like I am going to need to move records from one table to another and then again to another, deleting the original record from the 1st table and then the same thing with the 2nd table until it rests in the 3rd table.
I am pretty sure phprunner can do this with events - right?
Now, to do this, I will need a recruiter table, a employer table, a candidate table, a accepted table and a holding cell table. The employer chooses candidates from the candidate table and all the candidate fields move over to the holding cell table along with the employerID. When they do this, the candidate's record from the candidate table is now deleted. If the employer accepts the candidate, then the data is moved one more time to a table called accepted. The holding cell is emptied. If the candidate is not accepted, then the record is moved back to the candidate table.
Can this be done?
Mike
Sergey Kornilov admin 9/29/2010

Yes, this can be done with help of events.
Just a word of advice. In many cases you don't need to move data physically to another table. You can simply store everything in one table and update status field like 'posted', 'accepted', 'completed' etc.
K
 		karmacomposer author 9/29/2010



Yes, this can be done with help of events.
Just a word of advice. In many cases you don't need to move data physically to another table. You can simply store everything in one table and update status field like 'posted', 'accepted', 'completed' etc.


That is good advice. However, at the end of the year, the client wants to purge all records from the database of anyone hired. Those that were not hired need to remain. Can this be done without moving records?
Mike
Sergey Kornilov admin 9/29/2010

Yes, this can be done. It looks like a fairly straightforward deletion of all records with certain status.

delete * from <table name> where status='hired'
K
 		karmacomposer author 9/29/2010



Yes, this can be done. It looks like a fairly straightforward deletion of all records with certain status.

delete * from <table name> where status='hired'



Perfect.
I hope it's ok that I ask some questions as I create this - especially if I am going to use only a few tables.
Mike