UniverseUniversity


Home Projects Jobs Clientele Contact

uu


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

Re: course <-> topic, take 3



Well, since any topic can be made top-level topic that means - any topic may become a course by a simple connections transformation. If we need an extra fields - that may be done with the topic_description table, or something similar, that relates only to topic and nothing else.

2006/10/14, Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com>:
Actually let me add another thing:
this condition also applies to other tables, relating to the course.
I.E. if you need separate treatment/different data in ACLs
or some such depending on whether topic they link to is TLT
or not, we'll do the same.

Ilya A. Volynets-Evenbakh wrote:
> I'll accept that on one condition: this flag is going to be
> the only field that differentiates topic from course.
> I.E. if you feel the need to add more fields, that apply only
> to TLTs, you will move them out to separate table.
>
> Alexey Parshin wrote:
>
>> A simple logical conclusions.
>>
>> 1) Most of the properties of the course matching to the properties of
>> the topic.
>> 2) The difference between topic and course is the connections to other
>> objects
>> 3) Since any object can be connected to almost any other, the course
>> connections is just an extended version of topic connection.
>>
>> So, from any logical point, course is topic. We don't need to have a
>> separate object in the database for this. We may have  a flag
>> 'Top-level' in the topic, that allows an extra functionality for the
>> course.
>>
>
>

--
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com




--
Alexey Parshin,
http://www.sptk.net

Authoright © Total Knowledge: 2001-2008