March 23, 200619 yr Today, I was at a sales presentation for a software product that ties Autocad to a database. It became quickly apparent that they had the database very badly structured. I was trying to find the correct term for what they did, but in reviewing my books on relational theory, I couldn't find the term. Here is what they did: Consider a table that contains all the employee data for the London office. Now, suppose you add a Paris office. They create a second table with exactly the same fields as the first in order to hold the new data. New York office--same thing--new table. No way to create summary reports of all employees without some horrendous scripting. This is more fundamental than a normalization problem, but I'm at a loss as to what the correct term is for this kind of structure. Can any of you relational experts give me the correct technical term for this? I know what I'd like to call it, but it's not suitable language for polite company.
March 23, 200619 yr I've seen plenty of newbees asking for ways to duplicate their tables for just this purpose (one way that the copy/paste table ability of FM8 Advanced can be a trap for new developers.) For some reason people think their data will be safer if it's 'physically' separated like that, not looking at the maintenance and reporting issues this will cause. I just call it "duplicate tables", but LaRetta's sounds good too. }:(
March 23, 200619 yr LOL ... more apt given the mention of cities! On the serious side, I don't know what the term might be. "Normalization" came to mind, but I agree with Mr. Weaver the problem runs deeper than that. Structure is the most critical aspect of a database ... slick calculations might coexist within bad design, but can never overcome it.
March 23, 200619 yr I was just brushing up on this subject. I think you would call it duplicate/redundant 'entities,' but I like LaRetta's as well. -Raz
March 23, 200619 yr Author ...but I agree with Mr. Weaver... See that? Mr. Weaver, he says. I'll be expecting a lot more respect from the rest of you from now on. LaRetta, I like your term, but since I only used the cities thing as an analogy, I don't think anyone at the office would get the joke. Besides, I have to sound all professional like. So, "Duplicate/redundant" it is then. I hate coming across like a dufus when I'm talking to the IT department.
March 23, 200619 yr Well, I should say that I am much more confident about the 'entity' part than the 'Duplicate/redundant' part. There may be a more technical term specifically for this type of error, say, 'multiple entity disorder' or something... -Raz added- Here are a bunch of links to some fairly concise articles aout relational theory. Edited March 23, 200619 yr by Guest added a link
March 23, 200619 yr Besides, I have to sound all professional like. Oh. In that case, I'd use the term non-equi segmented redundancy. Techno-babble always makes their eyes glass over and you've got 'em. :girlgiggle: Good to see you around, you busy boy (ummm, Mr.); I miss your daily words of wisdom here on Forums. :wink2:
March 23, 200619 yr Yuk, yuk. That's good Bob. Giving amateurs tools like FM, which are 'too' easy to use, is kinda like giving a child a scapel and letting him perform brain surgery. Steve
March 23, 200619 yr LaRetta, I kinda dig your "Urban Sprawl". I couldn't resist this since I've found myself in such. How about "Intergalactic-exponential-data-growth?" Wikipedia gives an interesing explanation of "Exponential Growth" as "The phrase exponential growth is often used in nontechnical contexts to mean merely surprisingly fast growth..." which explains the growth (sprawl/creep) and intergalactic due to the physical space that you will need to bridge so as to make good use of the data.
April 7, 200619 yr When i was in the navy, we had a color nautical term for these types of things, but to mention it here would probabley get me censured by the forum gods.
May 3, 200619 yr LOL Abnormal Ani-Architecture .... Of course that brings us back to the beginning - Urban Sprawl he says so much with so little :
Create an account or sign in to comment