I'm creating an ER Diagram for a legacy database here.
I have a serious of tables that are different versions of the same
data. One is a 'Raw' copy of the current data, i.e. what the exact data
as it was received and input into the system. Another is the live data
after the raw data has been
These tables are not a child-parent relationship. They are
basically the same data with some variations of fields as
time goes on. Is there an ER standard to express this type
of relationship?
No, because there is no relationship between them, as relationships are
defined within a
Dave Watts wrote:
These tables are not a child-parent relationship. They are
basically the same data with some variations of fields as
time goes on. Is there an ER standard to express this type
of relationship?
No, because there is no relationship between them, as relationships are
Do you have a suggestion how one could document this type of
data model? I've since learned I may be making more of an 'data
model|diagram' rather then an entity relationship diagram even though
that is what Visio wants to call it.
I am trying to create documentation that shows how one
Ian Skinner wrote:
Dave Watts wrote:
These tables are not a child-parent relationship. They are
basically the same data with some variations of fields as
time goes on. Is there an ER standard to express this type
of relationship?
No, because there is no relationship between them,
Jochem van Dieten wrote:
If you want something better you should start with the data and put it
in a better schema:
That is the purpose of this documentation. I'm trying to document what
is so that I can start creating a better design.
That is the purpose of this documentation. I'm trying to
document what is so that I can start creating a better design.
Well, what is is essentially this (warning: ASCII art):
| table 1 | | table 2 | | table 3 |
|__|
7 matches
Mail list logo
