Joost Diepenmaat <[EMAIL PROTECTED]> wrote: > I'm moving an mmbase application from a postgres database to mysql - > which makes the whole application about 2.5 x faster - and I have a > question about indexes / constraints on the tables mmbase creates.
The would perhaps mean that your application is doing a lot of queries? > I've add a UNIQUE number_index (number) on every table, and it seems to > work just fine with this, but because mmbase doesn't do this itself, I > was wondering if this is actually supported, or that I should just use > KEY number_index (number) instead. Performance between them seems to be > about the same (on selects at least), but it's always a good idea to get > these contraints as strict as possible. I think we alway make unique key indices, and I think mmbase should principally make them itself. Are you using 1.7 with new storage layer? Michiel -- Michiel Meeuwissen Mediapark C101 Hilversum +31 (0)35 6772979 nl_NL eo_XX en_US mihxil' [] ()
