View Single Post
Old 09-07-2004, 12:27 PM   #1 (permalink)
feelgood
Free Mars!
 
feelgood's Avatar
 
Location: I dunno, there's white people around me saying "eh" all the time
[SQL] Normalization

I'm in the middle of a major school project that has been running from previous semester. We're in the design stage of a information systems which is probably a mickey mouse compared to the ones in the "real" world.

Anyways, my group and I are having disagreement regarding normalization of several database tables in MySQL.

Basically, what we have right now is 2 tables from the Conceptual ERD. They are Job Order and Product.

Job Order contains information about Products that are being made in the production line while Product contains information about products being sold as well parts needed to make the product. Parts can also be sold as a product.

Initially, after I reviewed the requirements regarding the Job Orders, I realized that there was no way for the user of the system to select part from a list of parts in the system and add it to the job order. Obviously, you need to have parts in order to make a complete product.

The original table looks like

{Job Order} >o-------------|- {Products}

This table was made based on that the Job Order table would contain the Product ID which is linked to Products.

When we factor in the fact that we need to have parts to be used for Job Orders. The table will look like this

{Job Order} >o-------------o< {Products}

This works fine in conceptual ERD but when we moved to implementation. The table would look like

{Job Order} >o------|- {Parts} -|-------o< {Products}

The justification for this was that parts table would contain Job Order ID, Product ID and Part ID. There is no product ID information in the job order table. The part id is actually the same information as product ID in the product table. I disagree with this.

I believe that, we don't actually need the product id in the parts table, but instead, put it in the Job Order table and have a Many to One relationship to the products table and keep everything else the same.

So, my idea will look like this:

{Job Order} >o------|- {Parts} -|-------o< {Products}
>o--------------------------|-

My main justification is that, if I wanted to know what the job order is making, why would I need to go through 2 different table (Parts -> Products) to find that out where I could simply just make a link directly to the products table.

My group member and course instructor is against me while I have my database instructor on my side.

What's your opinion?
__________________
Looking out the window, that's an act of war. Staring at my shoes, that's an act of war. Committing an act of war? Oh you better believe that's an act of war
feelgood is offline  
 

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360