Referential Integrity for TX_CUST_KEYWORD values

I have to assume my discovery is by design.

If I create an entry in "T_KWCODED_VALUES" and specify a value for the "key_value" field, then refer to that value by assigning it to a customer within the "TX_CUST_KEYWORD" table, then change the original value of the "key_value" field in "T_KWCODED_VALUES", then the "key_value" field in "TX_CUST_KEYWORD" is not automatically updated to match the modified value.

I am wondering how this is typically handled?  I am building some custom web code, and I want to join these two tables with the join clause partially conditioned by the "key_value" field.  But if I go into the T_KWCODED_VALUES table and change the value, then the attributes on the customer are not automatically updated, and so my join "breaks".

Is there a better way to do this?

Thanks!

Parents
  • Former Member
    Former Member $organization

    I would like a copy of that sql.

     

    Thanks, Trudy Guest,

    ArtTix Systems Administrator

    801.323.6969

    From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Larry Brindise
    Sent: Wednesday, July 27, 2011 9:32 AM
    To: Trudy Guest
    Subject: Re: [Tessitura Development Forum] Referential Integrity for TX_CUST_KEYWORD values

     

    I built a SQL update trigger for the T_KWCODED_VALUES table to enforce the referential integrity. If anyone's interested, ping back and I'll forward.

    From: Larry Brindise <bounce-larrybrindise9173@tessituranetwork.com>
    Sent: 7/26/2011 4:25:53 PM

    I have to assume my discovery is by design.

    If I create an entry in "T_KWCODED_VALUES" and specify a value for the "key_value" field, then refer to that value by assigning it to a customer within the "TX_CUST_KEYWORD" table, then change the original value of the "key_value" field in "T_KWCODED_VALUES", then the "key_value" field in "TX_CUST_KEYWORD" is not automatically updated to match the modified value.

    I am wondering how this is typically handled?  I am building some custom web code, and I want to join these two tables with the join clause partially conditioned by the "key_value" field.  But if I go into the T_KWCODED_VALUES table and change the value, then the attributes on the customer are not automatically updated, and so my join "breaks".

    Is there a better way to do this?

    Thanks!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

  • I don't want to post here yet because it is so new.  If you are comfortable with testing it a bit and assuming all risk, I'd be happy send it to you directly for your review.  Send me an e-mail to lbrindise@thephil.org and I'll reply with the code. ( I'm pretty sure that if I reply to the e-mail that the Tessitura Forum sent me, it will be posted here, which would be premature.)

    If you and any others review/test it, then I'll feel comfortable posting it here.  (Are there any Tessitura Network issues/rules with posting code?)

    I could put all the disclaimers in the world on it; "use at your own peril", etc, but even with that, I don't want to put something out there that does damage...not that I expect it to do damage...;)

    I will have this in production within a few days, so I'm confident I'll have something usable shortly. 



    [edited by: Larry Brindise at 10:57 AM (GMT -6) on 27 Jul 2011] Fixed my e-mail adderss.
  • Corrected e-mail

    lbrindise@thephil.org

    sorry for the extra quote in the link....I have a hair-trigger pinky on that single-quote button!

Reply Children
No Data