Re: Any new thoughts on OTLT (One True Lookup Table)

Laconic2 wrote:
> Consider the following code and description pairs drawn from a travel
> reservation system,
>
> <code>
> ("PA", "Pennsylvania")
> ("PA", "Pan American")
> </code>

Doesn't OTLT have to include a third column, 'class' perhaps, with values 'state' and 'airline' respectively?

Otherwise, you can't tell which row to use when displaying the lookup data for a state - and you could end up displaying 'Pan American' as part of someone's address.

-- 
Jonathan Leffler                   #include <disclaimer.h>
Email: jleffler_at_earthlink.net, jleffler_at_us.ibm.com
Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/