Hi –
A local requirement for migration to RT is to use our existing ticket
format, which is essentially YYYYMMDDsss where sss is a serial. It
will be easy to update the sequence/auto_increment in the database to
ensure that each day’s tickets are numbered correctly, but a number of
that magnitude is a long, not an int.
I’ve attached my new schema. When I go to create a new ticket now, I
get an empty error – through the web UI, it’s an “RT error” table
with no text in, and rt-mailgate returns
Create failed: / /
I also noticed that EffectiveId in the Tickets table remains NULL
rather than matching the id of the ticket as it does for tickets
created prior to the change.
I’m pretty much stumped as to where to go from here, and would
appreciate suggestions on figuring out exactly where things are going
pear-shaped.
Thanks,
-Rich
Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | Save The Pacific Northwest Tree Octopus
rich@lafferty.ca -----------±----------------------------------------------
schema.mysql.bigint-tickets (8.16 KB)