Re: Generalised approach to storing address details

> > Cimode: ... EAV is pure crap....
>
> If so, do you have any other suggestions, especially bearing in mind
> Bernard's remark about international requirements?

We can try a little experiment. If you would post a couple of typical addresses with different structures / order of fields, I can show how dbd's EAV-like approach would manage it. Others (Cimode?) can show non-EAV solutions. Then after the initial solutions are presented, you can specify additional new/different address structures that were initially unknown to see how each solution meets new data requirements. Neither approach is perfect. Each has it's advantages and disadvantages. If the ability to meet new/unknown data requirements is high on your list of importance, then your design will probably have some aspects of EAV and pay the price in terms of reduced dbms enforced constraints/performance and increased complexity of SQL/code. Received on Fri Dec 08 2006 - 16:53:29 CET