Vanja Bertalan wrote:
> If a fresh database is used for every new site, it's easier to recover if
> anything goes wrong (ie. corruption of data). It's possible to backup every
> database separately, and to recover it in the same manner.
Replication is going to be a help here if you want multiple sites in a
single
database.
> The down side would be that the admin interface has to be copied to every
> db. If any changes are made to the original admin interface it could be
> quite a hassle to update it in all existing databases.
> Further, could the number of persistent database connections be an issue?
The 1.2.6-beta2 has a new feature (of my hands, so I'm biased) called
SiteGroups
that addresses most of these issues.
With SiteGroups each record is marked with a group ID that could be
likened
to a database name. Each record is only available for the site visited
if
it matches the sitegroup of that host.
The external appearance is much like having the records stored in
separate
databases: in separate databases the DB server is the one enforcing the
separation
in SiteGroups the Midgard core handles that.
Each sitegroup have separate groups of users and an admingroup. One root
group
is defined that has global access.
Records can be labeled to be in the 'global' sitegroup which makes them
available
everywhere.
The two main reasons why I did sitegroups:
- bring down the number of required persistent DB connections
- With the admin site in the global sitegroup all changes I make to it
are available
to all clients, and the clients will still see only the records of
their own sitegroup
withing the admin site.
It's still in beta though. I haven't had any problems yet but I'd love
for some people
to bash on it till it breaks.
> If everything is done through the single database there are no problems with
> updateing the admin interface, but it seems to me that big problems could
> arrise if the data gets corrupted. It would be a problem to selectively
> restore backed up data. Possibly, all sites in the database could be
> affected, couldn't they?
Yes. Selective backup of SiteGrouped sites is much easier than multiple
normal sites
within one database since you can discriminate them on their sitegroup
label. If you
want to do single-site discrimnination you'll have to limit yourself to
one site per
sitegroup.
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]