I have developed an Internet traffic web tracking appliction for our company. Tools I used were obvious (at least to me): Apache, PERL, MySQL and Linux. As the project grew and clients started to like what they saw, new "ideas" started to pour to their heads. So, from something that was supposed to be simple, it will become a fully blown application.To be quite honest, the second approach looks more and more attractive to me because it seems like there will be less coding involved.My dilema:
They want to add more and more people using it (mostly managers) but they also want to limit access to certain areas of that database to some of them. The process is simple. They collect all the data using EchoScope and I do data mining for them. As you can imaging, they want to find out who is going to adult sites on company time and so on.Having said that, I think of two avenues I can take to solve this issue:
- Programmatically, using PERL
- Physically, seperating database into two tables. One with full privleges and the other with limited.
What do you think?
In reply to Which way to go? by bman
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |