Hi everyone,
We noticed that one of our availability reports was significantly off when calculating capacity and available seat counts. After some investigation I found that seat_num and seat_row in TX_PERF_SEAT were NULL for an extra 1760 seats for all performances attached to a specific facility. These seats don’t ‘exist’ in facility manager.
Counts were made accurate by adding a where clause in the SQL that eliminated them, however I’m a little perplexed as to how/why they got that way and if this is normal. Upon further digging, I found that we have thousands of them across a number of facilities.
Has anyone else ever seen this? Should I be concerned about them?
Natasha
Haha... and now I have discovered it. Tash - did you ever come up with anything?
Or, has anyone else seen this behavior?
Hey Frannie,
I meant to put in a support ticket about this, but didn't end up doing so. They didn't seem to be doing any harm, so I just wrote logic to exclude them. Best to put in a ticket if they are now causing issues.
Tash
Still don't seem to be doing any harm. We found another report calculating capacity using TX_PERF_SEAT but I added logic to fix, so I guess it's still ok.
If I ever figure out how it happened, I will update you!
Frannie
In T_SEAT, the table which holds the “master record” for any seat (and non-seat) in a facility seat map, the column is_seat will be equal to 1. A row in T_SEAT is not always an available location. It also contains a row for non-seat blocks, such as where seat map text characters are displayed.
You can JOIN to this table using TX_PERF_SEAT.seat_no to filter using T_SEAT.is_seat = 1.
=>Ryan Creps
@Tessitura Network
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Frances O'Connell Sent: Wednesday, August 27, 2014 6:39 PM To: Ryan Creps Subject: Re: [Tessitura Ticketing Forum] Extra entries in TX_PERF_SEAT
From: Natasha Purkiss <bounce-natashapurkiss5883@tessituranetwork.com> Sent: 4/16/2014 11:30:27 AM
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!
Hi Ryan,
Thanks for the tip. I actually had checked in T_SEAT for these phantom seats, and they all have a value of 1 in the in_seat column so that JOIN wasn't doing the trick either. I thought about setting that column to 0, but since I didn't have to to weed these phantom seats out, I decided against the update. Still just so curious as to how and why there were added...