Does PostgreSQL support replication?
There are several simple replication systems, DBMirror and RServ are part
of postgresql-contrib. For setting up RServ, see
I haven't tried any of them. There are many good reasons to use
PostgreSQL, though, and many good reasons to use MySQL, so it makes sense
to use a database interface layer in case we ever want to switch.
Well, to be entirely honest, I'd rather not use
the SourceForge CVS
server. It's cumbersome and full of problems.
I never had any problems with it. Once it's set up properly, it seems to
work reasonably well. You could also set up a project at BerliOS or
You definitely should use a CVS server if you expect any kind of
> Here is some other stuff that would be important
for a redesign:
> * have some kind of built in profiling
What exactly does this mean?
Keep a log of how much time is spent within each function so the parsing/
page generation process can be optimized accordingly. There are probably
ready-made CPAN modules for this.
> * have some better way to handle edit conflicts,
for example, CVS style
> * have a better way to handle discussions, e.g. "Post a comment",
> to this", but still do it using wholly editable wiki-pages
> * have a category system built right in, perhaps using a meta namespace
Already planned (though that latter one would be near
the bottom of the
Categories will likely go live soon (if Magnus finally finishes the damn
thing), so a compatible scheme needs to be in place if we want to switch
This seems to assume that images would have to be
stored in a file
system. I think it's better to store them in a database, possibly one
separated from the rest.
I never understood this approach. It only seems to be associated with
increased risks (reduced performance, increased risk of data corruption)
and have no benefits. What exactly is the disadvantage of just storing a
pointer to the local filesystem in the DB?
> * have a template system that can be used by the
> this could perhaps be combined with the general template system.
I have indeed planned such a template system, but
I'm not sure what you
mean by the "general template system". Is that referring to the site
skin system? I'd really rather keep those two separate. They are not
related enough concepts.
I do think there are similarities between the two. Any good template
system, for site skins OR for internal rendering, will have to support
things like loops, conditional blocks etc. This stuff needs to be parsed,
so you might as well use a single library for doing so.
You are using proper object-oriented design, I hope?