On Monday 07 June 2004 02:20 pm, Ken Jones wrote:
> On Monday 07 June 2004 2:01 pm, Jeremy Kitchen wrote:
> > On Monday 07 June 2004 01:39 pm, Martin Leduc wrote:
> > > Can you tel me quickly what is the difference between
> > > enabled-many-domain=y and =n?
> >
> > as far as I know it only affects sql (mysql only?) backends, as with
> > --enable-many-domains=y (default) it uses one table with all of the
> > information, and with it =n it uses one table per domain.
> >
> > Someone who has actually dug through the code (Tom?, Michael?, Ken?)
> > might be able to give you a more definite example, but from my experience
> > that's the main difference.
> >
> > I think --enable-large-site (or similar) is what enables/disables the
> > directory hashing, but don't quote me on that.
>
> As an ex-database admin, I wrote the many-domains=no option as
> an optimization to the database schema to save disk space.
>
> Consider hosting one domain with 1 million email accounts.
> The pw_domain(64 char) field is redundant (only one domain). So
> we would be wasting 64MB of space in the database. So instead
> the table is named after the domain.

I was about to ask you this but you ran off before I could.. so I'll just post 
for discussion purposes.

Isn't this what the varchar field is for?

-Jeremy

-- 
Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc.
  [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 847.492.0470 int'l
        kitchen @ #qmail #gentoo on EFnet ++ scriptkitchen.com/qmail

Reply via email to