• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Bad Data in Original Database

 
John Smith
Ranch Hand
Posts: 2937
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I recently downloaded my assignment and wrote a small GUI piece to view the data from db.db. Four records in the database have invalid data (such as 14:75 and 11:65 as times of departure and duration). I found a few messages in this forum refering to this, and the answers seemed to be to ignore the bad data and show it in the table as is. However, the fact that there are relatively many "bad" fields tells me that I should probably be expected to do some sort of validation, although it is not explicitely mentioned in the instructions. What do you guys think?
Thanks,
Eugene.
 
Scott Ramsey
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I noticed the bad data as well. I am leaving it as is but noting the fact that it is there in my design decisions document. I am justifying leaving the data alone on the basis that it is not the function of the application to ensure data validity of existing data, only of that which the user enters through the reservation system.
I don't know if that'll fly (I'm preparing to upload later this week....whew!), but any data cleanup efforts I could think of were not very elegant and rather arbitrary.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic