An DatabaseBackedContentBase would be a collection of wiki content stored in a database instead of in the file system (or other places).

If we really decide to do this, we should implement this as a kind of AbstractContentBase!

There's debate about whether this is need. Do we need it? Why?

The main reason I chose FlexWiki is that it specifically does not have a database backed content base. Please keep this wiki software simple if at all possible.

I think the ideal would be a data provider layer that makes it easy to set up most any data source - database, file system, or otherwise. That would make it much easier for folks to make the choice about where they want their data stored, as well as make it easier to "roll their own" data sources. -- RayDixon [28-Aug-04]

I would like to have a DatabaseBackedContentBase because our corporate web sites are hosted on a web farm. Trying to figure out how to replicate the file system storage and syncronize files is a nightmare.

I think it is always good to have the choice, but I would prefer to dump this install on a web host without a DB to install, point to and then unlink to snapshot.

I will be trying to use this software for my IT group to create tech notes. I will report back to see how it flys. DanBevivino [4Oct-05]