Realisation

I realised it wasn’t structural problem but that the same db now has two different logics. 

Inconsistency issue. Well, Either I picked one or I add another one? If I picked one, then the other will have minor issues. Occurrence won’t be that obvious but if you have one you will have two. It is a bet. Either one will have this issues. If I add another 1 meaning now there will be three kinds of logic. Not that sure if it will cause the issue but more like a combination of both. However, I cannot really assess the risk without any test by accessing the other two logics. I can only guess if that is the case. I guess this was what our instructor want us to have a group project for at least once but time instance was different so can only use reduction until the final logic is there. I just want to ensure mine wouldn’t cause the two problems but I also don’t want the other two to cause me mine. Sigh. This time didn’t spend too much time on ui but these sickening logic issues. Waste of time. I guess with the rushing of time, I will just proceed and leave the minor bug as it is. Major bugs mostly caught. Wasted time with deleting and reuse the seed data. Now should be me seeding the data so will go on to booking.