Paul Gillingwater wrote: > > Ah yes, that's what I meant in an earlier post. mgd_get_topic_by_name > > and mgd_get_topic are the same function these days. The number of > > parameters determines its behaviour. > > Yes, but it doesn't solve my problem, in that they both expect that > you know where you're starting from -- either you have a topic id, and > it looks for the names under that, or you specify the topic id you need. > > I understand that this is the way it is because of the relational structure > in the Midgard tables--I was just wondering if there's a better way > without walking the topic tree. Something along the lines of a "global" > mgd_get_topic_by_name() that will search in all topics.
We could, but topic names are not required to be unique across separate topics, so it'd be ambiguous. > Anyway, a follow-up question -- is it reasonable to recommend this > approach to new Midgard users, i.e., that Midgard will match a topic > to page if the name is the same? I think it makes things a little easier. I'd be reluctant to do so without also doing some rearchitecting (input appreciated). As noted it's not unambiguous, and the current setup doesn't quite fit into it. Just to satisfy my curiousity: why would you want to map topics/articles to pages? If you want meaningful urls, why not have the content in the pages themselves? Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
