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!
Making changes to standard Tessitura tables or procedures, including adding local triggers, is not something that the Network endorses or recommends. As Heather noted, these types of changes can be overwritten with a version patch or upgrade and such changes can lead to unexpected, and perhaps undesirable, results. While we understand the reason you have created the local trigger described in this thread, I thought it best to reinforce the Network’s stance to ensure there was no confusion.
Bob
From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Larry BrindiseSent: Wednesday, July 27, 2011 12:02 PMTo: Robert BellSubject: Re: [Tessitura Development Forum] Referential Integrity for TX_CUST_KEYWORD values
Yes, that's the table the trigger is on. I've named it
LT_T_KWCODED_VALUES_RefUpd_TX_CUST_KEYWORD
"LT" for "local trigger".
From: Heather Kraft <bounce-heatherlaidlawkraft3507@tessituranetwork.com>Sent: 7/27/2011 10:52:11 AM
Hi Larry -
Is this something that you've put on the t_kwcoded_value table itself? If so, just watch out for Tessi updates which *could* overwrite/drop and recreate the table/etc.
Other than that, sounds like a great idea. Would you mind posting the sql to your profile for sharing?
Heather
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!