There is currently no good way to do that. How unique does the
transaction id need to be? I mean, is it a problem if the id starts
from 0 when you restart the application? Is there a sort requirements
(larger transaction ids means later)?
Your solution doesn't work for remote connections. I suggest I add a
SQL system function that returns the current transaction id. What is
your preferred function name?
Is a String good enough, or is a byte array better? How fast does it
need to be?
Regards,
Thomas