On Thursday, June 17, 2021 at 2:40:05 PM UTC+2 Mat wrote: ... > title: adam >> barbara: mother >> caesar: father >> david: friend >> > ...
> > It will be hard to create an efficient algorithm with this setup, in > wikitext. You have 2 variables here. > > - The field name > > - The field value > > You need a configuration tiddler somewhere. .. This problem has been the > same for ages. > > What do you mean with "configuration tiddler" here? > In my "family" example, what would a config tiddler do or be - and why is > it problematic? > The algorithm will need some info about the possible relation values. eg: mother, father, friend, child, ... and so on. If it doesn't know what is possible it can't handle it. There is nothing problematic with config tiddlers. ... I just wanted to point out, that "freeform field names" is not a solution for the "relation problem" > Where would there be a problem with an "efficient algorithm"? > In your example, you use lists. Lists need filters and filters have to be fast. They can only be fast, if they internally don't have to make lookups in the wiki store. Especially if they have to touch every tiddler in the store. The core doesn't know about your structure eg: <name> : <relation> It already has some optimizations for <relation>: <name>, because there are probably more fields eg: father: xxx than xxx: father. In your OP xxx is a tiddler name and tiddler names are unique. so there will be only 1 xxx field and all the relations have to be looked up, which is slow. -mario -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/e6ca7ee7-a068-447d-b69d-3118286c2707n%40googlegroups.com.
