The problem the community faced last week, which led to the mixing up of ticket dates, is actually the "Update Anomaly" we just mentioned. In this broken system, when the date of an event changes, the date data in the row of each student who bought a ticket for that day has to be updated manually, one by one. This is what happened in the scenario we were told: Naturally, while trying to enter so much data, people weren't as careful as the computer, and some rows were overlooked during the update. As a result, two different date records were created in the system for the same event, and due to the lack of coordination, 00 students were unfairly unable to attend the event.