• (nodebb)

    Well, the last two times I traveled by train, coaches were not available since they just went part of the train, so my reservations basically disappeared into thin air. No delays, no cancellation - just a train with missing coaches. But I have to say a concurrency issue is similar frustrating, didn't happen to me (yet).

  • NotABigDeal (unregistered)

    Another option is that when a race condition double-booking happens, it is no big deal. Just something that is quickly and easily worked out on the train as happened in the article. Both passengers were happy they got to they were going with an amusing story to tell, so they never reported a bug.

  • Tinkle (unregistered)

    TRWTF is not applying for a refund (which would force them to fix the booking system,) or the train company not charging to reserve a seat (unlikely.)

  • Scragar (unregistered)

    This is why DB consrraints are important even if you have logic in code.

    If the DB didn't allow two people on the same train to have the same seat then one transaction would fail. That's annoying when you're the person who has to reselect their seat or retry, but it's better than knowingly allowing bad data to exist.

  • klinsten1 (github)

    Clearly this did not happen in Belgium... the real WTF would be taking the train and expecting everything to go smoothly and without delay

Leave a comment on “Racing Trains”

Log In or post as a guest

Replying to comment #705150:

Log Out

« Return to Article