Hello, About a month ago we discussed mgd_list_calendar_all here and I think the conclusion was that it was exclusive. That is, if it was given a start date and end date only articles starting and ending within those dates where returned. Articles that started before but ended within or started within but ended after the timeframe where ignored.
As a workaround for a simple event calendar, I have thought about selecting articles in php instead. By requesting mgd_list_topic_articles_all() and then with a while loop and some compares of $article->calstart and $article->caldays select the articles inclusively for monthly and weekly listings. But now I wonder what a list_all function does to the performance of midgard. When does midgard and the function mgd_list_articles_all (ie the "walk subtrees too" version") begin to "feel slow"? Is it when a topic tree has 100 or 1000 or 10 000 articles? I have a rather fast server, athlon 1.4Ghz with 512MB (hopefully soon 1024 =) memory. At what load (how many articles?) do you believe the list_all() will start to bog down and make page requests take several seconds, instead of milliseconds as it is now? BTW, does anyone have any other way to make inclusive selects of articles? -- Fredrik Jonson [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
