Custom Fields again
bbaetz at student.usyd.edu.au
Wed Dec 11 14:13:16 UTC 2002
On Wed, Dec 11, 2002 at 06:44:18PM +0500, VFedrushkov at chel.LUKoil.com wrote:
> > Why is it a Big Deal? Or rather, why should it be a Big Deal?
> Because we don't want custom fields to be 'cheap'. Instead we
> encourage administrator to think well before doing that.
Think of what? If someone wants a <foo> field, then, well, they want one
> And yes, if custom fields reconfiguration would require me to take
> database offline, I'd first look how to implement desired feature
> within standard functionality.
Well, the point is that with custfields this will become standard
OTOH, I'm not sure how long it would take to change the schema, even on
bmo - even with extrenal tables we still have to insert an entry for
every row (for some types, at least), and thats not cheap.
More information about the developers