Hi
I just went over and re-read the datamodel and the two data dictionaries.
First question, which data dictionary do you want? If the answer is the
'alternative', then shall I change the model to match.
Now, pushing forward I also saw what it was that sat funny with me, when
first I read the doc's.
In the LOAN table you have the following columns:
dateloaned date
datedueback date
datereturned date
returned boolean
OK, well if I might suggest. datedueback would not be a field I would
ever use in a working DB. Instead I would have a policy table, or entry
in a table that gives me the number of days an item can be loaned out
for. Then the datedueback becomes a calculated value only. In the case
of the example database, it might give a very good reason to show the
use of a VIEW.
Another small point, using both datereturned and returned together is
IMO redundant. The returned (boolean) field serves no real purpose for
the check datereturned <> NULL is the same as returned = TRUE and
dateretuened = NULL is the same as returned = FALSE.
Sincerely
Andrew Jensen
