IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Okay, so here I am making an indeterminate
Relationship with tables.

I have three tables.

AddressDetail, ZipCodeInfo, CarrierRoutes.

The relationships:

AddressDetail.ZipCode -> ManytoLessMany -> CarrierRoutes.ZipCode -> ManytoLessMany -> ZipCodeInfo.ZipCode

AddressDetail.CarrierRouteID -> ManytoLessMany -> CarrierRoutes.CarrierRouteID (with implied AddressDetail.ZipCode -> ManytoLessMany -> CarrierRoutes.ZipCode)

It this Sane? (Yes, I relaize Many to less Many isn't a real relationship, but I think it is easier to think of it that way rather than Multiple Many to One relationships)
--
[link|mailto:greg@gregfolkert.net|greg],
[link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @ iwethey
[image|http://www.danasoft.com/vipersig.jpg||||]
New Why have the zip in 3 seperate tables?
Perhaps have one table that stores off addresses and have the other tables foreign key the addresses from there?
New Table record number are in teh Millions already
In details at least, the zip and carrier could be combined, unfortunately they have different tables columns in them tha would be like a cartesean join... 20 different ways.
--
[link|mailto:greg@gregfolkert.net|greg],
[link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @ iwethey
[image|http://www.danasoft.com/vipersig.jpg||||]
New What's the primary key in CarrierRoutes?
Is there a unique index in CarrierRoutes?
===

Purveyor of Doc Hope's [link|http://DocHope.com|fresh-baked dog biscuits and pet treats].
[link|http://DocHope.com|http://DocHope.com]
New Record number.
There are so many Carrier Routes that are the same, but for different ZipCodes...

Awww, feck it all. The Address Details has everything I need, I just have to compute totals and sorting by. It ain't worth the effort to join this stuff.

Of course... I could do all left joins. See as I only know them.
--
[link|mailto:greg@gregfolkert.net|greg],
[link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @ iwethey
[image|http://www.danasoft.com/vipersig.jpg||||]
New So CarrierRouteId+ZipCode is unique?



"Whenever you find you are on the side of the majority, it is time to pause and reflect"   --Mark Twain

"The significant problems we face cannot be solved at the same level of thinking we were at when we created them."   --Albert Einstein

"This is still a dangerous world. It's a world of madmen and uncertainty and potential mental losses."   --George W. Bush
New Yessir
Indeed that is what is unique.
Never had to use a Multi-field primary key.
--
[link|mailto:greg@gregfolkert.net|greg],
[link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @ iwethey
[image|http://www.danasoft.com/vipersig.jpg||||]
New It happens
and you can use it that way if it is immutable. Otherwise replace it with a generated key and add a constraint.



"Whenever you find you are on the side of the majority, it is time to pause and reflect"   --Mark Twain

"The significant problems we face cannot be solved at the same level of thinking we were at when we created them."   --Albert Einstein

"This is still a dangerous world. It's a world of madmen and uncertainty and potential mental losses."   --George W. Bush
     Okay, so here I am making an indeterminate - (folkert) - (7)
         Why have the zip in 3 seperate tables? - (ChrisR) - (1)
             Table record number are in teh Millions already - (folkert)
         What's the primary key in CarrierRoutes? - (drewk) - (4)
             Record number. - (folkert) - (3)
                 So CarrierRouteId+ZipCode is unique? -NT - (tuberculosis) - (2)
                     Yessir - (folkert) - (1)
                         It happens - (tuberculosis)

Where is a super volcano when you need one?
87 ms