Stephen R. van den Berg writes:
The common way to solve this which does not cost extra database space would be to store a unique but permanent identifier per aox instance, and then use a one-way-hash (e.g. MD5) to make your UUIDs difficult to guess (it only needs to fill in part of the UUID this way; the message number itself could still be transparently present).
I'm not concerned about database space, but requiring an extension feels ungood. However, the number of aox users is now in two digits and probably dropping, and they all are capable of adding an extension, so IMO it's fine either way.
Stephen, feel free to merge this patch if you think the migration step looks reasonable (ie. with an error message like that in stepTo96()).
Arnt
