Re: Overriding derived values
- From: Hugo Kornelis <hugo@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 29 Nov 2005 23:43:29 +0100
On 29 Nov 2005 12:47:16 -0800, dawn wrote:
(snip)
>Other than the use of the numerical codes (why not text codes?) I agree
>with your redesign. One question -- does the owner of the system ever
>want the discount to be overridden for more than a month? For example,
>in your scenario where someone has stolen, it seems like there should
>be a DENY code on this bowler indefinitely -- until it is changed.
>There is no reason to set this each month and plenty of reason not to
>introduce a possible failure by insisting it be set each month.
Hi Dawn,
Good point.
I'd favor a design with override code, override start date and override
end date. That makes it easy to enter a 6-month denial after stealing or
a 4-month guaranteed discount for winning a match against the competing
bowling club from the other side of the street.
For indefinite bans or discounts, set end date to either NULL or to a
silly date in the distant future, like 9999-12-31.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)
.
- Follow-Ups:
- Re: Overriding derived values
- From: mAsterdam
- Re: Overriding derived values
- References:
- Overriding derived values
- From: Ira Gladnick
- Re: Overriding derived values
- From: dawn
- Overriding derived values
- Prev by Date: Re: Fast SQL Question
- Next by Date: Re: Overriding derived values
- Previous by thread: Re: Overriding derived values
- Next by thread: Re: Overriding derived values
- Index(es):
Relevant Pages
|
|
