While I agree that it's evil, I didn't have anything to do with it. I just have to deal with it now : )
However, I don't see how your suggestion could deliver the same functions. Basically, the columns in Table1 are named for actions one could perform on an appointment and the comma seperated lists are the products one would perform those actions for on a given appointment which is detailed by that row. Though the number of actions is fixed (relatively), the products vary with every appointment. so how does your structure above provide the ability to have varying products associated with any number of actions and also correlated to one another as a coherent appointment? I've been staring at your tables and can't quite get it...
-- I'm a solipsist, and so is everyone else. (think about it)
In reply to RE: RE: reversing a hash -- printing it
by jptxs
in thread reversing a hash -- printing it
by jptxs
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |