Custom fields schema

Christopher Hicks chicks at
Sun Jan 23 14:13:13 UTC 2005

On Sun, 23 Jan 2005, Gervase Markham wrote:
> But what happens at this stage, in the real world, is that no-one has time to 
> rip out the schema and start again, and lots of people have made local 
> modifications which would break anyway, and so we all grumble about how we 
> should have got it right the first time, and live with the bad 
> implementation.

Look at all of the database tweaks in and tell me we're 
prone to just live with it and not tweak it into shape over time.

> While deciding on the correct approach should not delay the 
> implementation of custom fields indefinitely, I think that doing some 
> up-front design is a perfectly reasonable step on the way to 
> implementation.

The design has been out there for ages and now people are just ripping 
apart one section - the database design's affect on performance - which 
was actually done correctly already.  If there's some other "up-front 
design" that's needed, what is it?


"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)

More information about the developers mailing list