These are discussion posts posted by students, I am required to reply to them in a logical manner in a paragraph or two The following is the question...

These are discussion posts posted by students, I am required to reply to them in a logical manner in a paragraph or two

The following is the question asked by the professor: "There is a humorous saying: To error is human, but it takes a computer to really mess things up! I imagine we've all had the unfortunate experience of seeing the truth of that saying at our place of work. Describe an example of a very poorly implemented database that you've encountered that illustrates the potential for really messing things up. Include in your description an analysis of the design errors that might have caused the problems. "

I have already written a discussion in response to this assignment however, I also have to respond to these four other discussion posts.

The following are below

Number 1

One of my first jobs directly out of undergrad was working alongside a group of other young developers to build an application for a local jail.  One of the main aspects of this system was to keep track of the visitation of the inmates.  So to accomplish this we had three tables, one that held data for the inmates, one that held data for the visitors and one that linked the tables together and also logged date and time information.  

Everything was going well after the initial implementation, until an issue came up where a visitor happened to become an inmate. This happened quite frequently and resulted in a lot of duplicate records across the 'Visitor' and 'Inmate' tables