What is the table "tw_sli_detail_bypass" for? We had an error report from Ticketing with a duplicate key value (on the SPID). Closing Tessitura and reopening it fixed the issue. The one record in that table also was deleted when Tessitura closed.
I'm just looking for some context on this.
There are cleanup routines that run at client shutdown and client startup to flush out expired work table entries that may exist for the user’s current or previous sessions. Work table entries are nearly always cleared up when a process is complete (e.g., when an order is saved), but they can linger if the something occurs while in process (i.e, network hiccup, db connection failure, app crash). Most often, simply restarting the app will cause this data to be flushed.
+Ryan Creps
+Tessitura Network
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Crowell Sent: Thursday, April 4, 2013 9:50 AM To: Ryan Creps Subject: Re: [Tessitura Technical Forum] tw_sli_detail_bypass?
Okay. Thanks!
So her instance of Tessitura didn't shut down cleanly or something. _shrug_
From: JD Short <bounce-jdshort2095@tessituranetwork.com> Sent: 4/3/2013 1:54:59 PM
Tables prefixed 'TW_' are temporary work tables used to store data which is then moved to a permanent table later in the Order (or Contribution) process.
Sometimes, when web or imported orders are created, a spid_no/order_no combination is written to the TW_SLI_DETAIL_BYPASS table to let the system know that the process will be creating the sli_detail rows. Typically, those combinations are deleted when the order creation is complete.
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!