Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Data Modeling "the third way ?"
Others have responded with the technically correct explanations, so from a
"theoretical" point-of-view :)
This is what you get when you ask a programmer to help design a database. There is a name for the design method chosen: "WRM", or "Wheel Reinvention Modeling".
"Dario Rossa" <dario.rossa_at_mature.be> wrote in message
news:b515b4da.0304101021.36434d67_at_posting.google.com...
> Hi,
>
> Few days ago I head a discussion on data modeling.
> To me , at least what I know about data modeling there are two ways
> (or two families) to model "the real world" the data of your business
> model.
> 1. Dimensional modeling , Star Schema....
> 2. Entity Relationship modeling , ERD , 3NF ..or E-ER modeling..say
> the OO way.
>
> But he had following modeling technique...
>
> - No relationships between tables.
> - Table A contains in one of the columns the name of the related table
> - Table A contains the record number of the related table, mentioned
> in the column above.
>
> It seems to me that this is not maintainable and to get or insert data
> you almost need to implement a database engine yourself to update
> record numbers...etc.
> No mapping possible to EJB CMP or whatever technology to retrieve or
> store data.
>
> His argument is : It is flexible...you can store everything...
>
> But what are you modeling....This is not a model to me and not usable.
>
> Happy to hear some comments on this one...."the third way"
>
> //The truth is out there
>
>
> Regards,
>
> Dario
> dario.rossa_at_mature.be
Received on Fri Apr 11 2003 - 08:24:14 CDT