-----BEGIN PGP SIGNED MESSAGE-----
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.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
-----END PGP SIGNATURE-----