<div>
<div>
<div>I hate to reply to my own question, but does anyone else see this issue with new tickets being generated with IDs of n+10 rather than n+1? It has to be something simple/stupid that I'm missing, but I've been looking at it for days and am clearly overlooking something at this point...I offer a 6 pack of your choice of beers in exchange for a quick fix :)
</div>
<div> </div>
<div>cheers,</div>
<div>mike<br> </div></div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div> </div>
<div><span class="e" id="q_11248cae141cd4ff_1">
<div><span class="gmail_quote">On 4/30/07, <b class="gmail_sendername">mike</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:mike@bseder.org" target="_blank">mike@bseder.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>Hello,</div>
<div> </div>
<div>Since upgrading to RT 3.6.3, I've noticed that all of our tickets are incrementing their ticket numbers/IDs by n+10 - </div>
<div> </div>
<div>From show table status:</div>
<div> </div>
<div>| Tickets | InnoDB |10 | Compact | 14823 | 248 | 3686400 | 0 | 1146880 | 0 | 24632 | 2007-04-30 09:35:08 | NULL | NULL | latin1_swedish_ci | NULL | </div>
<div> </div>
<div> </div>
<div>And the table itself (sorry for the mangling....):</div>
<div> </div>
<div>mysql> describe Tickets;<br>+-----------------+--------------+------+-----+--------------+----------------+<br>| Field | Type | Null | Key | Default | Extra |<br>+-----------------+--------------+------+-----+--------------+----------------+
<br>| id | int(11) | NO | PRI | NULL | auto_increment | <br>| EffectiveId | int(11) | NO | MUL | 0 | | <br>| Queue | int(11) | NO | MUL | 0 | |
<br>| Type | varchar(16) | YES | | NULL | | <br>| IssueStatement | int(11) | NO | | 0 | | <br>| Resolution | int(11) | NO | | 0 | |
<br>| Owner | int(11) | NO | MUL | 0 | | <br>| Subject | varchar(200) | YES | | [no subject] | | <br>| InitialPriority | int(11) | NO | | 0 | |
<br>| FinalPriority | int(11) | NO | | 0 | | <br>| Priority | int(11) | NO | | 0 | | <br>| TimeEstimated | int(11) | NO | | 0 | |
<br>| TimeWorked | int(11) | NO | | 0 | | <br>| Status | varchar(10) | YES | | NULL | | <br>| TimeLeft | int(11) | NO | | 0 | |
<br>| Told | datetime | YES | | NULL | | <br>| Starts | datetime | YES | | NULL | | <br>| Started | datetime | YES | | NULL | |
<br>| Due | datetime | YES | | NULL | | <br>| Resolved | datetime | YES | | NULL | | <br>| LastUpdatedBy | int(11) | NO | | 0 | |
<br>| LastUpdated | datetime | YES | | NULL | | <br>| Creator | int(11) | NO | | 0 | | <br>| Created | datetime | YES | | NULL | |
<br>| Disabled | smallint(6) | NO | | 0 | | <br>+-----------------+--------------+------+-----+--------------+----------------+</div>
<div> </div>
<div>Have I missed something simple? The version of RT I upgraded from also used InnoDB tables, so it doesn't seem to me to be an issue with auto_increment strangeness with InnoDB tables (which I've read a little about). Any clues?
</div>
<div> </div>
<div>Thanks!</div>
<div>Mike</div><span>
<div> </div>
<div> <br>--<br>One way or another, everyone stops bleeding. </div></span></blockquote></div><br><br clear="all"><br></span></div>--
<div><span class="e" id="q_11248cae141cd4ff_3"><br>--<br>One way or another, everyone stops bleeding. </span></div></blockquote></div><br><br clear="all"><br>-- <br>--<br>One way or another, everyone stops bleeding.