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

[Daniel Breitner]

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

[Roel De Nijs]

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]

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 ?

[Bernd Wollny]

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]

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

That's the spirit

Kind regards,
Roel