Re: Insurance data models...any tips on good starting point?

"aai_jj" <jjohnson_at_grafikchaos.com> wrote in message news:3b272948-42c1-457e-b964-72a2afc637bc_at_y38g2000hsy.googlegroups.com...
> We have a client that has the typical online quote generator but is
> looking to revamp that process and tie it in with other services he
> can sell to other insurance clients. The application is still in its
> infancy but could have the potential of blowing up in our face if we
> don't plan accordingly.
>
> The old website used a fairly simple RDB with a lot of array
> manipulation done by the developers, but we'd like to make it a little
> more object-oriented, maybe even consider an EAV modeling approach to
> allow for the growth.
>
> Are there any insurance data models out there to start from or is
> anybody willing to share their experience on similar projects?
>
> Any thoughts or direction would be greatly appreciated.
>
> Thanks.
>

What benefits would you expect to gain from an EAV appraoch? What downside do you expect to pay with an EAV approach? How will you deal with that downside?

(You probably know that most regulars here in comp.databases.theory view EAV as a pretty bad design principle. That includes me.) I'm just including this so that, in case you have already thought of the issues in cost&benefit terms, we can save a little time. Received on Thu Jul 10 2008 - 22:35:18 CEST