[rt-users] SelfService interface probs

[Josh Richards]

* Robie Basak <robie at principle.co.uk> [20020814 01:50]:
[..]
> Thinking about it, I can make a guess as to what's happening.
> 
> One instance of Apache handled the first request (to create the ticket
> or whatever). That corresponding instance of RT created the ticket
> inside a database transaction, and committed it.
> 
> Then, another instance (hence definitely a different db handle) did a
> query. There's no guarantee that the transaction will yet be seen by
> anyone else, because transactions either get seen or don't. So
> presumably the database was still busy with it, and would've only shown
> it's existence to the previous instance.
> 
> So, if I'm right, using the same db handle consistently would fix it.
> I'm not sure if that corresponds to running a single apache process or
> not, but whichever way it would hit performance.
> 
> Or the second instance should wait until the first's transaction
> appears, but there's no guarantee that it will because you could've
> requested to view an invalid ticket.
> 
> I suppose that's just an example of why web-based interfaces aren't
> ideal for these things, though unfortunately it's the best we have at
> the moment.
[..]

Hmm...maybe a well situations sleep(x) would take care of it? :-)  You
think?

-jr

-- 
Josh Richards <jrichard@{ digitalwest.net, geekresearch.com, cubicle.net }>
Digital West Networks, Inc. - "Making Internet Business Better"
San Luis Obispo, CA - <URL:http://www.digitalwest.net/> - ASN 14589