[rt-users] How to modify the ticket # format?

[Ken Crocker]

Tom,

    Why do you need a date prefixed to the Ticket ID? In my 40 years in 
this business from Manufacturing (MRP - Order processing, Capacity 
Planning, etc.)) to Retail to Banking industries I have always seen an 
ID Field defined as "non-intelligent". That way, the ID has one function 
only, to identify the record, not to define when (that's what dates are 
for). To put intelligence or some other meaning into a field that is 
designed for a singular purpose is pretty much considered a very 
outdated practice (for last 25 years) in DataBase design (ie. each field 
is used strictly for a single purpose and it's name indicates such 
function). Are you sure you want to design the Ticket ID this way?


Kenn
LBNL

On 5/11/2009 12:56 PM, Tom Lahti wrote:
> Ruslan Zakirov wrote:
>   
>> http://wiki.bestpractical.com/view/SetStartingId + cronjob to set it
>> everyday, however you must understand limits on integers in your DB.
>>     
>
>   
>>> Example: #200905110001  would be the 1st ticket for today.
>>>       
>
> A normal signed int in 32-bit mysql has a maximum value of 2147483647, which
> isn't big enough for the format requested.  You'd need to alter the table
> structures to change ticket id's to a bigint.  How much code that would
> break inside of RT, I have no idea.
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20090511/2b497275/attachment.htm>