tag:blogger.com,1999:blog-15861274.post113951132409098769..comments2023-09-18T11:14:24.509+01:00Comments on Oracle WTF: EAV Returns: The Concrete Elephant approachWilliam Robertsonhttp://www.blogger.com/profile/06976436975493102341noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-15861274.post-1161944868830548892006-10-27T11:27:00.000+01:002006-10-27T11:27:00.000+01:00CommentCommentAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-15861274.post-1139829428906453412006-02-13T11:17:00.000+00:002006-02-13T11:17:00.000+00:00There is a genuinely difficult problem that guy is...There is a genuinely difficult problem that guy is trying to solve here.<BR/><BR/>Not all application development is bespoke to a clients needs, so in the situations where flexibility is required while maintaining some sort of 'core' code base, some sort of extensibility needs to be built into the solution. It just isn't always practical or desirable to redesign the application schema for every additional column.<BR/><BR/>One of the key things that customers nearly always say in their requirements or RFPs is that they require the flexibility without resorting to the vendor for code changes.<BR/><BR/>The 'Concrete Elephant' solution proposed here is clearly nonsense, however an approach where the core entities, their attributes and entities are modelled in the schema itself, but whereby some felixibility is introduced by allowing the addition of attributes using an attribute-value approach does have some merit.Rab Boycehttps://www.blogger.com/profile/07598095845411214782noreply@blogger.com