On Tue, Jun 16, 2009 at 12:50:28PM +0100, Greg Stark wrote:
> On Mon, Jun 15, 2009 at 2:04 PM, Gnanam wrote:
> >
> > I also read some article which talks about the type of patterns:
> > 1. Meta-database
> > 2. Mutating
> > 3. Fixed
> > 4. LOB
> >
> > My question here is, what is the best approach t
On Mon, Jun 15, 2009 at 10:21 PM, Sim Zacks wrote:
> From the user's perspective: If you design an application for me and I
> want to add a new data field or a new form, should I have to call you
> back and pay your exorbitant consulting fees? I would prefer to pay a
> little bit more at the begin
On Mon, Jun 15, 2009 at 2:04 PM, Gnanam wrote:
>
> I also read some article which talks about the type of patterns:
> 1. Meta-database
> 2. Mutating
> 3. Fixed
> 4. LOB
>
> My question here is, what is the best approach to define the architecture
> for custom fields. Performance should not be compr
Custom fields are a fact of life, and used in many, many business
critical applications. EAV sucks, as you mentioned, but that doesn't
take away from the requirement to build that kind of system.
>From the user's perspective: If you design an application for me and I
want to add a new data field o
On Mon, Jun 15, 2009 at 10:37:04PM +0200, Stefan Keller wrote:
> @David: You wrote in the links cited "The "flexibility" stems from
> fear of making a design decision.". That's an important note.
> Nevertheless, there are use cases where you *can not* know in
> advance what the name is of the attr
@David: You wrote in the links cited "The "flexibility" stems from
fear of making a design decision.". That's an important note.
Nevertheless, there are use cases where you *can not* know in advance
what the name is of the attribute! To me that's not fear but
adaptiveness, modesty and knowing when
On Monday 15 June 2009, Gnanam wrote:
> Hi,
>
> I'm designing a database schema in which I should allow user to create
> custom fields at the application level. My application is a web-based
> system and it has multiple companies in a single database. So this means
> that each company can create
On Mon, Jun 15, 2009 at 06:04:25AM -0700, Gnanam wrote:
>
> Hi,
>
> I'm designing a database schema in which I should allow user to create
> custom fields at the application level.
This is called EAV (Entity-Attribute-Value), and it's a
multi-decade-old mistake. Re-think your design.
http://ar
