10
ultrono
6y

So, today timestamps within my database saved me. I have one titled "created_at" to indicate when the item was originally created.

Today a large client called up to complain that they have 296 bookings but only 288 menu choices (each booking has a menu choice). Basically, saying I'd "programmed it wrong [sic]" :(

After taking a quick look at the date the client originally added the menu and the date the missing bookings were created, I made a discovery.

It turned out the client was at fault. They had set an event (customers book events and bookings have a menu choice) live without associating the menu. This meant the event had been live without a menu for customers to book.

I simply compared the timestamps of the missing bookings to the date the menu was originally added. The customer most likely made the event live for period (I estimate ~45 mins), realised they hadn't associated a menu and then added it afterwards. Of course at this point it was too late as people had already booked.

No need for a huge email either. I condensed the above into a 5 sentence email.

Timestamps are soooo useful

Comments
  • 2
    Yes they are always life saver.. we have auto generated timestamps of created at and also maintain auto on update timestamps for modified on and an extra security feature have a modified by could be either code / user logged in who did it.. these are all life savers for debugging..
Add Comment