|
|
Posted by bbcrock on 03/06/07 18:08
On Mar 5, 11:02 am, "myke.dil...@gmail.com" <myke.dil...@gmail.com>
wrote:
> I think there are a couple of ways you can go here. First is an
> assessment of what the business logic behind the TRANSPORTATION_ITEM
> table is. If it simply for output for the interface then move the
> business logic up into code. If that is not possible, or there is
> truly data that needs to be saved for another purpose, the the other
> route would be to add the TRANSPORTATION_ITEM id to the truck and
> train table. That should give you the normalization you require and
> reduce the NULL fields in the TRANSPORTATION_ITEM table which is what
> it appears you are really after. Then your query can join the from
> the train or truck table to the TRANSPORTATION_ITEM table.
Yeah, I was really unclear when I wrote that initial post- I had to
get it out and move onto something more pressing. There is a one to
many relationship where truck and train "types" are used in multiple
transportation_item records. So that would increase the amount of
truck records if I included transportation_item in that table.
thanks!
Navigation:
[Reply to this message]
|