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 :)
cheers, mike
On 4/30/07, mike <[EMAIL PROTECTED]> wrote: > > Hello, > > Since upgrading to RT 3.6.3, I've noticed that all of our tickets are > incrementing their ticket numbers/IDs by n+10 - > > From show table status: > > | Tickets | InnoDB |10 | Compact | 14823 | 248 | 3686400 | 0 | > 1146880 | 0 | 24632 | 2007-04-30 09:35:08 | NULL | NULL | latin1_swedish_ci > | NULL | > > > And the table itself (sorry for the mangling....): > > mysql> describe Tickets; > > +-----------------+--------------+------+-----+--------------+----------------+ > | Field | Type | Null | Key | Default | > Extra | > +-----------------+--------------+------+-----+--------------+----------------+ > > | id | int(11) | NO | PRI | NULL | > auto_increment | > | EffectiveId | int(11) | NO | MUL | 0 > | | > | Queue | int(11) | NO | MUL | 0 > | | > | Type | varchar(16) | YES | | NULL > | | > | IssueStatement | int(11) | NO | | 0 > | | > | Resolution | int(11) | NO | | 0 > | | > | Owner | int(11) | NO | MUL | 0 > | | > | Subject | varchar(200) | YES | | [no subject] > | | > | InitialPriority | int(11) | NO | | 0 > | | > | FinalPriority | int(11) | NO | | 0 > | | > | Priority | int(11) | NO | | 0 > | | > | TimeEstimated | int(11) | NO | | 0 > | | > | TimeWorked | int(11) | NO | | 0 > | | > | Status | varchar(10) | YES | | NULL > | | > | TimeLeft | int(11) | NO | | 0 > | | > | Told | datetime | YES | | NULL > | | > | Starts | datetime | YES | | NULL > | | > | Started | datetime | YES | | NULL > | | > | Due | datetime | YES | | NULL > | | > | Resolved | datetime | YES | | NULL > | | > | LastUpdatedBy | int(11) | NO | | 0 > | | > | LastUpdated | datetime | YES | | NULL > | | > | Creator | int(11) | NO | | 0 > | | > | Created | datetime | YES | | NULL > | | > | Disabled | smallint(6) | NO | | 0 > | | > > +-----------------+--------------+------+-----+--------------+----------------+ > > 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? > > Thanks! > Mike > > > -- > One way or another, everyone stops bleeding. > -- -- One way or another, everyone stops bleeding.
-- -- One way or another, everyone stops bleeding.
_______________________________________________ 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
