• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

what about the 48-hours rule ?

 
Andy Jung
Ranch Hand
Posts: 150
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

my assignemt says (URLyBird 1.1.2:
They take bookings only within 48 hours of the start of room occupancy.

What does this "only within 48 hours" imply?
Doesn't this mean, that if the equation
now + 48 hours < available date
ist true, that I have to avoid booking because of the stated rule?

And since most booking dates in the given database are in the past, booking wouldn't be possible anyways?
This is why I implemented the update-functionality for all fields as well, because if you want to book, you have to make sure:
  • 1. there is an available room with a date in future (because booking rooms in the past just doesn't make sense)
  • 2. enable booking only, if it takes place within 48 hours up to the availability date


  • Kind regards,
    Andy
     
    Roel De Nijs
    Sheriff
    Posts: 10662
    144
    AngularJS Chrome Eclipse IDE Hibernate Java jQuery MySQL Database Spring Tomcat Server
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Hi Andy,

    In my code I just ignored this rule I explained in my choices.txt why I didn't implement this rule (and for completeness: it had nothing to do with the content of the database file).

    Kind regards,
    Roel
     
    Andy Jung
    Ranch Hand
    Posts: 150
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Hi Roel,

    yes I think it's legal to ignore this rule, because it is not a "must"-requirement.
    But no matter which way you handle this,
    you should mention it in your choices.txt (because this is a problem or uncertainty) and document it in the user guide as well.

    Kind regards,
    Andy
     
    Roel De Nijs
    Sheriff
    Posts: 10662
    144
    AngularJS Chrome Eclipse IDE Hibernate Java jQuery MySQL Database Spring Tomcat Server
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Hi Andy,

    It should only be in the user guide, if it is implemented and it might be the reason why a booking failed. If you decide not to implement it, you should not mention it in the user guide (so in my user guide you'll find nothing about 48 hours rule)

    Kind regards,
    Roel
     
    Andy Jung
    Ranch Hand
    Posts: 150
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Hi Roel,

    are you sure this shouldn't be mentioned in choices.txt, because it was an uncertainty to me?

    Kind regards,
    Andy
     
    Roel De Nijs
    Sheriff
    Posts: 10662
    144
    AngularJS Chrome Eclipse IDE Hibernate Java jQuery MySQL Database Spring Tomcat Server
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Maybe I wasn't clear enough in my previous post: it should always be mentioned in choices.txt, but should only mentioned in user guide if it is actually implemented (and might be a reason why booking could fail for example)
     
    • Post Reply
    • Bookmark Topic Watch Topic
    • New Topic