On Tue, Jun 30, 2009 at 4:28 PM, Jesse Vincent<[email protected]> wrote: > On Tue, Jun 30, 2009 at 03:06:17PM -0500, Dusty Wilson [Megagram] wrote: >> 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. >> 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. _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [email protected] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
