Home Projects Jobs Clientele Contact


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

Re: UMO Find: More exclusion parameters

Circular dependencies will be a problem if we implement
a "workflow" - when student has to "complete" one UMO
before passing on to studying next one. We could postpone
circular dependency detection until we start implementing
workflows and only enforce it there..

For now implement object skip based on base_id.

Alexey Parshin wrote:
> I understand how we can find a single object to exclude when looking for
> linking - it's just link object base. That implementation is trivial.
> I don't think excluding any more objects makes sense. Circular dependencies
> cause no negative reaction with Anatoly - I've asked him a while ago.
> 2009/1/8 Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com>
>> I think we might want to provide exclusion
>> parameters for umo_find:
>> If we are searching for objects to link to,
>> we might want to pass list of parent objects
>> which shouldn't show up on results (in this case,
>> I think we are passing umo_base IDs).
>> Alternative: if we already have logic for
>> completely disallowing circular deps inside database,
>> we could pass single base ID - for intended parent,
>> and then filter out all of possible trees from results.
>> --
>> Ilya A. Volynets-Evenbakh
>> http://www.total-knowledge.com

Ilya A. Volynets-Evenbakh

Authoright © Total Knowledge: 2001-2008