[rt-users] Ticket missing from database

[Mike Friedman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've just put RT 3.4.2 into production and have noticed something 
interesting.  One of the tickets that had been created earlier is no 
longer in the database!  At least it can't be accessed via RT. Yet other 
tickets with higher numbers are there.  I have not done anything directly 
against the (MySQL) database (such as run RTShredder) that would have 
removed the ticket.

Any idea how this can occur?  It's possible that the ticket was marked 
with status 'deleted', but it shouldn't be gone from the database.

As it happens, this messes up one of my perl scripts, that displays all 
tickets with status 'deleted' in a range of ticket numbers, but stops as 
soon as a ticket can't be loaded, on the assumption that this means I've 
passed the largest ticket number currently in RT.  It would be nice if I 
could continue to rely on that assumption, at least as long as I don't 
intentionally remove tickets from the database.

Thanks.

Mike

_____________________________________________________________________
Mike Friedman                   System and Network Security
mikef at ack.Berkeley.EDU          2484 Shattuck Avenue
1-510-642-1410                  University of California at Berkeley
http://ack.Berkeley.EDU/~mikef  http://security.berkeley.edu
_____________________________________________________________________

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA+AwUBQ4s7Y60bf1iNr4mCEQLOngCYgGRS87I8yLEx0BCU6qxF6tJV5wCgz1lI
I5m6Wk3F8kUs5f18V2W1U2k=
=xPZD
-----END PGP SIGNATURE-----