Subject | Re: [ib-support] Performance Issue Solved |
---|---|
Author | Todd Brasseur |
Post date | 2002-12-07T17:49:05Z |
The reason the two codes are separate is because the single code has a
foreign key to a CODES table and the COMBINATIONCODE has a foreign key
to a COMBINATIONCODE table. The CODES table is simply a a Code and a
Name. The COMBINATIONCODE is quite complicated in that it can be made
up of up to 6 combinations of CODES from the CODES table.
Todd
Doug Chamberlin wrote:
foreign key to a CODES table and the COMBINATIONCODE has a foreign key
to a COMBINATIONCODE table. The CODES table is simply a a Code and a
Name. The COMBINATIONCODE is quite complicated in that it can be made
up of up to 6 combinations of CODES from the CODES table.
Todd
Doug Chamberlin wrote:
> At 12/07/2002 12:39 AM (Saturday), Todd Brasseur[Non-text portions of this message have been removed]
> <todd@...> wrote:
> >First of all, thanks to everyone for your responses to my problem.
> >Today I found the problem and I will try to explain in case anyone
> >else runs into the same thing.
> >[details snipped]
>
> Thanks for posting the resolution for us. I'm glad you got past the
> problem!
>
> One other thought: I don't know if this will work better for you but you
> might consider combining the two rate tables again but with a slightly
> different structure. In the new table have a Code and Rate field but
> add an
> "IsSingleCode" field to indicate if the Code field represents a
> SingleRate
> or CombinedRate value.
>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
> <http://docs.yahoo.com/info/terms/> .