SharkD wrote:
> I think a relational database system is the wrong tool to use in this 
> case... Just use it to store the data *after* it has been processed and 
> normalized.

Well, except I want to re-run the query whenever things change.

But yes, I'm coming to the conclusion that there's no good way to represent 
this. On the other hand, since I have no requirements either, I'm not too 
worried yet.

-- 
Darren New, San Diego CA, USA (PST)
    C# - a language whose greatest drawback
    is that it's best implementation comes
    from a company that doesn't hate Microsoft.

Post a reply to this message