SQL sequel

Results 1 to 6 of 6

Thread: SQL sequel

  1. #1
    anonymous Guest

    Default SQL sequel

    I&#039ve got a small issue with coding a SQL statement for an application that dispenses raffle tickets.<BR><BR>We&#039ve got 200,000 tickets to sell, but obviously we do not want to sell the same ticket twice. Likewise we want to make sure that the full 200, tickets are sold.<BR><BR>The issue arises when a shopper orders 20 tickets, we flag them as held, and write a log to a tracking_table.<BR><BR>Anyways, now the shopper enters the checkout phase, and, low and behold they have &#039insufficient funds&#039, or, worse still, they just kinda&#039 order them and never checkout.<BR><BR>Now, we know Session_OnEnd is a bit buggy, so how do I ensure that these tickets are freed up for re-sale.

  2. #2
    Steve Cimino Guest

    Default Contract Ticketmaster!

    Have you considered using MTS? For instance, no money, then SetAbort. That will free up the tickets in the table again.

  3. #3
    Skippie Guest

    Default RE: SQL sequel

    Create a shopping cart table unless you already have one.<BR><BR>When the shopper fails to purchase the tickets, then "unflag"<BR>the tickets, then empty his cart.<BR><BR>-- Skippie

  4. #4
    Skippie Guest

    Default RE: SQL sequel

    You could also "un flag" the tickets that have been in the cart<BR>for more than a specified amount of time, like 24 hours.<BR><BR>-- Skippie<BR>

  5. #5
    anonymous Guest

    Default RE: Contract Ticketmaster!

    Thanks, this looks like the best long term solution.

  6. #6
    lagerBoy Guest

    Default RE: SQL sequel

    Thx, we&#039ve considered using the AT command and Windows Scripting Host to schedule a VBS file at certain intervals. This appears to be workable for a project of this size.<BR><BR>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts