Jonathan Walther wrote:
I like the Wikipedias version of what it is to be a "Wiki", and want to use it for many other projects, groups, and committees. For that purpose, I am doing the redesign, so I and others can easily deploy the Wikipedia software in a wide variety of contexts.
There are other wiki software projects that aim at a broad range of uses. This one is for running wikipedia. If others can use it too, fine. Focus should remain on wikipedia.
So, whether Wikipedia ever uses it or not, I am doing this. But I want to ensure that we COULD host the Wikipedia on it. And because it is written in C as a custom Apache module, with Postgres backend, I will be able to make it very fast and efficient.
OK, I understand that, and though I don't have experience with Postgres, I agree about the C part. I wrote a C++ wiki parser as proof-of-principle once, and it was fast as hell on my local machine, compared to the PHP software (which was using cached pages!). It got lost in some systems crash or Linux update, though ;-)
If we switch to Postgres, to get the benefits of Postgres we must do a redesign of the table schema, at least. Did anyone notice that Postgres is now fully SQL92 compliant? And a redesign of table schema means we can design it so that generating a regular wiki page only involves ONE query, instead of the current TWELVE. A long term redesign of the software could definately be beneficial.
Now *that* would really help!
Magnus