Quote:
|
Originally Posted by sonofsam
|
Sonofsam, as you most likely know MPA3 has been out now for about 2 years, following MPA2 ? the two programs are completely separate and MPA3 was written new from scratch.
In the time when we upgraded clients from MPA2 to MPA3 we made sure that ANY possible shaving mechanism would be removed and replaced with the opposite ? an anti shaving feature that would allow us for the most part to easily see if a client added code that could mess with the MPA3 code in any way shape or form.
Trax is right in what he is saying. This was a code that we had to add to remove any shaving that was in the mpa2. So when our old customers upgraded we were removing any module like this using this particular script with the inane name of ?no_shaving_update.sql? ? we have written upgrade scripts that were copying the table structure over to mpa3 database as they are. Should we have named is something else to avoid gfy threads like this?
StuardD ? you seem like a smart guy ? you are right on track and that is exactly what that file did. This file was used to remove anything associated with the old mpa2 shave feature. And the file is mostly in older MPA3 versions where this was a necessity to ensure that all upgrades or new installs were squeaky clean, which they all are. Newer versions will not have this file in it to begin with.
Anyone who understands a little SQL would see that this is what this code is doing, and I believe that having a no shaving was something everyone wanted, not the opposite.
Now, if there are still some conspiracy theorists out there that still want more info on this ? come into my office, let?s have you pick out any random MPA3 client and ask for their permission to review their source code with us. Anyone welcome of course.