remove faulty logic in update code

I imagine this change was a first stab at handling MSSQLs very strict rules on circular cascades, however the logic is now incorrect (especially since cascades are completely cleared out when detected to be false).