Re: UMO interface functions

[Anatoly Volynets <av@total-knowledge.com>]

Alexey Parshin wrote:
> I'm not sure if we can attach any UMO to any other UMO. For Instance -
> attaching a topic to an explanation, or attaching an explanation to
> problem
> doesn't make much sense to me.

That is right and we don't have it in specs, and we don't need it. OTOH,
we probably want plain references (like html links) to be included
anywhere in texts, e.g. in the problem statement or problem solution. Is
this possible?

If yes, what such link may refer to? If I want to tell (just want!
Author may want to tell such things) that this problem may cause
difficulty if you (student) haven't studied such and such courses?

What happens, when a student in the middle of work with an UMO goes
astray along said kind of links?

>
> In the present structure of the database, we have only certain
> connections
> between UMOs allowed. If we need ANY-2-ANY type of connection - then
> we need
> a different DB structure.
>
> 2007/4/29, sergey@total-knowledge.com <sergey@total-knowledge.com>:
>>
>> Regarding topic_attach_to_topic() and topic_detach_from_topic() types of
>> stored procedures.
>> Since most of the UMOs(like problems, tests, dialogs, etc) can be
>> attached
>> to any other UMO except themself, imho it makes sense to have only 2
>> attach/detach stored procedures:
>> umo_attach() and umo_detach().
>> Attach should be performed only if child UMO is allowed to be attched to
>> provided parent UMO.
>>
>>
>> > It's not going to work for every UMO. For example, problems have more
>> > complicated functionality. Also course is much different from others.
>> >
>> >> Hello,
>> >>
>> >> It looks like we have to standardize the set of the UMO functions.
>> Here
>> >> is
>> >> the typical list that is implemented for topic_list,
>> topic_explanation,
>> >> and
>> >> dialog_of_texts:
>> >>
>> >> GRANT EXECUTE ON FUNCTION <UMO>_create(int,varchar(80),text) TO
>> PUBLIC;
>> >> GRANT EXECUTE ON FUNCTION <UMO>_delete(int) TO PUBLIC;
>> >> GRANT EXECUTE ON FUNCTION <UMO>_create_version(int) TO PUBLIC;
>> >> GRANT EXECUTE ON FUNCTION <UMO>_publish_version(int) TO PUBLIC;
>> >> GRANT EXECUTE ON FUNCTION <UMO>_add_content(int,int,varchar(80),text)
>> TO
>> >> PUBLIC;
>> >> GRANT EXECUTE ON FUNCTION
>> <UMO>_modify_content(int,int,varchar(80),text)
>> >> TO
>> >> PUBLIC;
>> >> GRANT EXECUTE ON FUNCTION <UMO>_delete_content(int) TO PUBLIC;
>> >> GRANT EXECUTE ON FUNCTION <UMO>_attach_to_<parent
>> >> UMO>(int,int,int,int,int)
>> >> TO PUBLIC;
>> >> GRANT EXECUTE ON FUNCTION <UMO>_detach_from_<parent UMO>(int,int) TO
>> >> PUBLIC;
>> >>
>> >> Please, notice: In order to match this standard I had to modify names
>> of
>> >> few
>> >> topic_* functions, related to content and attach/detach.
>> >>
>> >> --
>> >> Alexey Parshin,
>> >> http://www.sptk.net
>> >>
>> >
>> >
>> >
>>
>>
>>
>
>

-- 

Anatoly Volynets, Co-Founder
total-knowledge.com
culturedialogue.org