![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
*twitch*
WHY oh WHY would you NOT UPDATE your browser from Netscape 4.77?! This is an academic library that runs Win2KPro and we provide the latest IE and allow you to download and install anything you want! Why the HELL would you choose to use - and we don't supply it so you HAD to download it special - the BUGGIEST SUCKIEST MOST HORRIBLE BROWSER OF THEM ALL?!
And why am I even CONSIDERING changing this webpage so that it works especially for ONE EMPLOYEE instead of authoritatively insisting that she use a working browser? I've diplomatically suggested she change, explaining that Netscape is out of production, suggested a browser thatr would preserve the look and feel she's used to, and told her to ask my coworker to help her install it to keep all her bookmarks and settings, but she's actively not taking the hint.
In other words, the beta version of the event-scheduling app I've been working on went live today and while there have been many small bugs, easily ironed out except for the above which I really consider user error in the case of this closed system, there have been no major database errors, which was the problem with the old one.
And the REAL reason the old one was throwing all the errors? As the page constructed the graphical calendar to the side, it hit the databse for *every* *single* *day* just to check if there were any events on that day so it could bold the date number if there were (pointless - lots of people use it, so of *course* every date has events). So every page had at minimum, 33-35 database hits per load (dates plus display) - and the page had a meta-refresh so it reloaded every couple of minutes if you had it open. I haven't figured out how to use temp tables or table variables yet, so I still hit the db multiple times with every page load, but I have max five or six database queries per page. Oodles better than 30+.
And why am I even CONSIDERING changing this webpage so that it works especially for ONE EMPLOYEE instead of authoritatively insisting that she use a working browser? I've diplomatically suggested she change, explaining that Netscape is out of production, suggested a browser thatr would preserve the look and feel she's used to, and told her to ask my coworker to help her install it to keep all her bookmarks and settings, but she's actively not taking the hint.
In other words, the beta version of the event-scheduling app I've been working on went live today and while there have been many small bugs, easily ironed out except for the above which I really consider user error in the case of this closed system, there have been no major database errors, which was the problem with the old one.
And the REAL reason the old one was throwing all the errors? As the page constructed the graphical calendar to the side, it hit the databse for *every* *single* *day* just to check if there were any events on that day so it could bold the date number if there were (pointless - lots of people use it, so of *course* every date has events). So every page had at minimum, 33-35 database hits per load (dates plus display) - and the page had a meta-refresh so it reloaded every couple of minutes if you had it open. I haven't figured out how to use temp tables or table variables yet, so I still hit the db multiple times with every page load, but I have max five or six database queries per page. Oodles better than 30+.
no subject