Home Projects Jobs Clientele Contact


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: UU database: problem tables

Still, the question "Should we drop the course entity and replace it with topic" still not answered.And, I still see no reason for limiting a course to a single topic.
I can see a course with multiple topics, and don't see any problems with it.

2006/9/26, Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com>:
Alexey Parshin wrote:
> 2006/9/26, Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com
> <mailto:ilya@total-knowledge.com >>:
>     On a related note, problem (just like any other object actually)
>     can belong to more then one topic, more then one test, etc.
>     Same is true for topic->subtopic relationship.
>     On the other hand, there is 0-1:1 relationship between course and
>     topic. I.E. like we talked about earlier, course is just an
>     administrative
>     unit, wrapping single top-level topic.
> Why a course may have only one topic? I probably missed something, but
> I see no reason why course may not have several topics.. Otherwise, we
> don't need two entities for the same thing.
Read this thread:

Ilya A. Volynets-Evenbakh
Total Knowledge. CTO

Alexey Parshin,

Authoright © Total Knowledge: 2001-2008