• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

URLyBird - 48 hours and old entries - what do you think ?

 
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello everybody,

I was just wondering how to deal with this two situations:

1) A record in my database will be available in - say - 70 hours.

I thought of two approaches:

a) Filter out the record so that no csr will ever see it

b) donĀ“t filter it out and present an error message when this record should be booked

I tend to b ...


2) A record is outdated

I thought of deleting it. Therefore I would start (for example) a seperate thread iterating over the database and deleting all "old" entries


What do you guys think of that ?

btw: Merry Christmas

Daniel
 
Sheriff
Posts: 11604
178
Hibernate jQuery Eclipse IDE Spring MySQL Database AngularJS Tomcat Server Chrome Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Daniel,

1. I know some people implemented your option b. I just ignored this 48 hours business rule (and provided an argumentation in my choices.txt why I didn't implement that business requirement). So it's up to you to decide which approach you prefer: I would suggest not implementing it, but if you do I would opt for option b (and that's the one I would implement myself too).

2. No requirements to do something like that. So just don't do it (maybe these "old" records are used by another application to take statistics and your application simply deletes them).

Merry Christmas!

Kind regards,
Roel
 
Daniel Breitner
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
OK, thanks for your answers

One more question:

I have read my assignment once again and found nothing about an "Un-Book" - Button.

Did you guys implement one ?
 
Ranch Hand
Posts: 59
Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Daniel,

if there's nothing said about an unbook function, it's not a must requirement. So just let them be booked forever...

Kind regards
Bernd
 
Roel De Nijs
Sheriff
Posts: 11604
178
Hibernate jQuery Eclipse IDE Spring MySQL Database AngularJS Tomcat Server Chrome Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Bernd Wollny wrote:So just let them be booked forever...


That's the spirit

Kind regards,
Roel
 
Get meta with me! What pursues us is our own obsessions! But not this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic