Hi all, There is a way to use graphviz extension in templates? (MW 1.5.x) tnx Marco

On 19/06/06, Marco Rota <marcor(a)sorint.it> wrote: Install the extension plus dependencies, then insert appropriate markup into the desired template page. Rob Church

On 19/06/06, Marco Rota <marcor(a)sorint.it> wrote: Contact the writer of the extension and ask them to support wiki markup as part of the extension input? Rob Church

Moin, On Monday 19 June 2006 18:03, Rob Church wrote: That would be complicated, and probably not work for something like: <graph output="{{{1}}}"> [ A ] -> [ B ] </graph> anyway. So, is/will/can there be a way that template parameters are replaced properly inside extension tags or their parameters? Best wishes, Tels -- Signed on Mon Jun 19 18:24:22 2006 with key 0x93B84C15. Visit my photo gallery at http://bloodgate.com/photos/ PGP key on http://bloodgate.com/tels.asc or per email. Q: "Dr. Fisher, how did you begin your great career in Contact Dermatology?" Dr. Alexander Fisher: "I started from Scratch!"

On 19/06/06, Gregory Szorc &lt;gregory.szorc(a)gmail.com&gt; wrote: Wikimedia have been telling porkies since 2004, then? Rob Church

On 6/19/06, Rob Church &lt;robchur(a)gmail.com&gt; wrote: I thought Wikimedia uses MySQL replication, not clustering. MySQL clustering uses main memory to store tables. Somehow I don't think the Wikimedia servers have that much memory. BTW, MySQL 5.1 will finally support disk-based clustering. Even then, there is still the issue of FULLTEXT indexes in cluster mode. Does the cluster storage engine support FULLTEXT indexes? Greg

Hello, You're slightly wrong. We have enough memory to store our mysql core database in memory. Yes, for non-indexed data. We don't use FULLTEXT indexes on live site anyway. It's pure InnoDB, and search is offloaded to Lucene. Anyway, Cluster is designed to handle zillions of small transactions per second without data loss, it could work as a solution for session storage (and it is used that way on several biggish sites). On the other hand, our access pattern would not like distributed database that much as there're quite a lot of batch reads. We already solve the 'clustering' by simply having replicated sets of database nodes working with different workloads / patterns if needed. We're quite happy with current setup, I guess ;-) Domas

[...] With replication, there is only one writeable node. How do you force mediawiki to do reads from replica #n and writes to the master? -- Daniel J McDonald, CCIE #2495, CNX, CISSP #78281 Austin Energy gpg Key: http://austinnetworkdesign.com/pgp.key Key fingerprint = B527 F53D 0C8C D38B DCC7 901D 2F19 A13A 22E8 A76A

Daniel J McDonald wrote: Code that works with the database asks the load balancer for a database connection object that's either the master (for write or time-sensitive read work) or a randomly selected not-too-lagged slave (for non-sensitive read work). See LoadBalancer.php. -- brion vibber (brion @ pobox.com)

Daniel J McDonald wrote: Yes; we're not losing sales if the site's partially broken for a few minutes, so it hasn't yet been worth it to invest time and money in setting up automatic transparent failover for something that's very rare. Likely not; because reads need to function properly even when slaves are slightly lagged, some items will check the master. For instance, on a page view the tiny 'page' record is read from the master, then revision metadata, text, and link-coloring information are pulled from a slave. Otherwise you can edit a page and have it serve you back the previous version -- which we don't want then stuck in a cache! -- brion vibber (brion @ pobox.com)