Ticket ID as CHAR(32)?

I just sent an email about UNSIGNED INT for the database. This is a
separate (but related) question: Is there a reason why ticket IDs
can’t be CHAR(32)? I’d love to use a proper UUID as a ticket ID.

If I convert a UUID from hex (base 16) to alphanumeric (case
sensitive: base 62; case insensitive: base 36), I can use much less
space to store the UUID.

Anyone have any thoughts on that?

Thanks,
Dusty

I just sent an email about UNSIGNED INT for the database. This is a
separate (but related) question: Is there a reason why ticket IDs
can’t be CHAR(32)? I’d love to use a proper UUID as a ticket ID.

That’s going to break an awful lot of assumptions in RT’s code. Primary
keys are integers. And Ticket Id is as primary as they come. I’d be
interested to see patches, but you’re going to have your work cut out
for you.

I just sent an email about UNSIGNED INT for the database. This is a
separate (but related) question: Is there a reason why ticket IDs
can’t be CHAR(32)? I’d love to use a proper UUID as a ticket ID.

That’s going to break an awful lot of assumptions in RT’s code. Primary
keys are integers. And Ticket Id is as primary as they come. I’d be
interested to see patches, but you’re going to have your work cut out
for you.

Are you aware of anywhere that the code does anything with that ticket
ID other than pass it around? I haven’t yet (but haven’t done deep
digging) seen it being used for anything other than in the queries
themselves and displayed on the web UI and emails. My change from
signed int(11) to unsigned int hasn’t seemed to cause any trouble thus
far. I’m willing to do the work if it doesn’t seem unreasonable to
want this.

Are you aware of anywhere that the code does anything with that ticket
ID other than pass it around? I haven’t yet (but haven’t done deep
digging) seen it being used for anything other than in the queries
themselves and displayed on the web UI and emails. My change from
signed int(11) to unsigned int hasn’t seemed to cause any trouble thus
far. I’m willing to do the work if it doesn’t seem unreasonable to
want this.

Yep. Transactions, Custom Fields, Ticket Linking are the first three big
things. We never use negative numbers, so switching from signed to
unsigned is safe. When you start making your mods, you’ll want to make
sure you’re running the test suite.