<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Tom,<br>
<br>
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?<br>
<br>
<br>
Kenn<br>
LBNL<br>
<br>
On 5/11/2009 12:56 PM, Tom Lahti wrote:
<blockquote cite="mid:4A0882DD.8050503@bitstatement.net" type="cite">
<pre wrap="">Ruslan Zakirov wrote:
</pre>
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-freetext" href="http://wiki.bestpractical.com/view/SetStartingId">http://wiki.bestpractical.com/view/SetStartingId</a> + cronjob to set it
everyday, however you must understand limits on integers in your DB.
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Example: #200905110001 would be the 1st ticket for today.
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
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.
</pre>
</blockquote>
</body>
</html>