> Well, thousands of tables is probably "too much", but a hundred tables or two
> in a database shouldn't cause problems. Don't see why you'd want them though.
If that's your general advice (a hundred or more tables in a
database not making sense) I should like to learn why. Is that
a sure sign of overdesign ? Excess normalization ? Bad
separation of duty ? I am asking since our schema is at
about 200 relations and growing.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
