hello emile, thanks for your answers,
> recompile midgard-lib. You can admin multiple databases with asgard > (for example) but you'd need Asgard in each since Asgard doesn't work Since I'm almost only working with asgard this is no problem > with multidb. Technically Midgard can admin a site in one db using a > host in another but it carries some limitation in Midgard > functionality for the adminsite involbed and asgard (nor nadmin, btw) > work with those limitations. The problems may arise while using different mgd_ handles. I will give some reports later ... > > performance improvement. But splitting of the midgard databases becomes > > already important if two sites had no chance for synchronized tables > > from the project start. > > Synchronized tables? should better be named consistent tables after migrations of records. > Just use a separate MidgardDatabase directive for those VirtualHosts. > You can run an adminsite in a separate database using the > MidgardPageDatabase directive, but as I said, none of the current > admin sites work with this (although oldadmin requires only a few > simple changes) Smaller migrations should be run by copies of single records. Bigger migrations will require constantly kept in different databases. However the best argument should be performance as mentioned in the manual. bye, dieter -- Kind regards Dieter Heine Systemadministration Unix Astrium GmbH Raumfahrt Bremen EMail: [EMAIL PROTECTED] Fax: 49 421 539 5698 Phone: 49 421 539 4989 User Help Desk Astrium Hamburg Phone (office Bremen): on request --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
