On Mon, Sep 13, 2010 at 5:09 PM, Daevid Vincent <daevid@xxxxxxxxxx> wrote: > > > > -----Original Message----- > > From: tedd [mailto:tedd@xxxxxxxxxxxx] > > Sent: Sunday, September 12, 2010 9:32 AM > > To: PHP-General list > > Subject: 1984 (Big Brother) > > > > Hi gang: > > > > I have a client who wants his employees' access to their online > > business database restricted to only times when he is logged on. > > (Don't ask why) > > > > In other words, when the boss is not logged on, then his employees > > cannot access the business database in any fashion whatsoever > > including checking to see if the boss is logged on, or not. No access > > whatsoever! > > > > Normally, I would just set up a field in the database and have that > > set to "yes" or "no" as to if the employees could access the > > database, or not. But in this case, the boss does not want even that > > type of access to the database permitted. Repeat -- No access > > whatsoever! > > > > I was thinking of the boss' script writing to a file that > > accomplished the "yes" or "no" thing, but if the boss did not log off > > properly then the file would remain in the "yes" state allowing > > employees undesired access. That would not be acceptable. > > > > So, what methods would you suggest? > > > > Cheers, > > > > tedd > > You sure know how to pick'em Tedd. > > This is the second "whacky" client you've posted about on the list... > > This guy sounds like a real control-freak (read: tool). > > One other thing I'll throw out is the use of a crontab to start/stop mysql > during "boss's hours". I don't have a complete solution for you as I just > don't care enough about helping this Dbag lord over his employees like > that, but I suspect you could have "/etc/init.d/mysql start" or "stop" at > some pre-determined times like 8am - noon. Then noon till 5pm. Or > something. > > RDBMS are not really designed to be turned on and off like that. > > Another option is to maybe use M$ Access instead (which does have a > multi-user mode). Use ODBC to connect via PHP to it. So then he would start > up the DB when he likes and shut it down when he likes. (note that a logout > of Windows will NOT prevent the ODBC connection as it is a service -- as > God intended RDBMS to be) > http://www.configure-all.com/php_access.php > > This guy is making me angry just thinking about it! > > d > > Yes I've been following this post purely in the hope that someone gets Tedd is explain the client's "logic" on this one. It's one thing for a layman to have this kind of requirement, but another entirely for them to STILL have it after an explanation. I mean part of consulting is to tell the client when they're wrong, for someone to not heed that when they are paying for the advice is mind boggling. *sigh* if only everyone were perfect like me... :p "Hey lets pay someone to consult us on a subject that we're ignorant of." "Great idea! And when he makes a suggestion we can totally ignore him! SQL - Shmeequal" Rant aside; I would defer the logistics to the client. He wants the DB to shutdown when he's not in the office? Ok no problem - not what it was designed to do, but no problem! "How would you like the system to be aware of rather or not you're in the office? It can assume you are between these hours; You can log into a screen that unlocked it, but then you have to logout; we can put a motion detector in your office; ... etc." This would put the consequences of the system off on the client. Because if this system works then there will be consequences and you'll look like a jerk :-) Btw, are there no cron / batch jobs that need to run over night? Chris
