-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
When we moved from RT 2.0.15 to 3.4.2 a while back, we decided not to
carry over our old tickets. Instead we just built a new RT with a fresh
database. But in order to avoid confusion with our ticket history, we
told RT3 to begin ticket numbering at a higher number than that of the
last RT2 ticket (i.e., we started RT3 with ticket #60000).
Now we’d like to see if we can move the RT2 tickets (we’re still running
RT2 on another machine) to RT3, preserving their old ticket numbers
(which are unused numbers in RT3).
Is there a safe way to do this? Could we, for example, temporarily reset
the ticket id auto-increment starting value from 60000 to 1, feed the old
tickets in with their original numbers, then reset the auto-increment
starting value back to 60000? Would new tickets subsequently created
start at the next available number after our highest RT3 ticket number, or
would RT get confused because it would try to start creating new tickets
with number 60001?
I have a feeling this will cause problems, but I’d like to find out for
sure.
Of course we can always move the tickets from RT2 to RT3 with newly
assigned ticket numbers, but it would be preferable for us if we can
preserve the old ticket numbers in the new RT, for tracking purposes. (I
know, we should have thought of all this at the time we upgraded!).
Thanks.
Mike
Mike Friedman System and Network Security
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
http://ack.Berkeley.EDU/~mikef http://security.berkeley.edu
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBQ/JPxa0bf1iNr4mCEQK1nACg/ksChQVEAWbolYb7Gz0G1gYwK08Ani0B
V5HZSl7IIHXhsBCOcv/OovB9
=igSW
-----END PGP SIGNATURE-----
I suspect that you’ll run into problems with transaction numbers. In
fact, I’m quite certain of this. I would call this a BAD idea,
especially if you want all data preserved such as creation and last
updated dates.
Mike Friedman wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
When we moved from RT 2.0.15 to 3.4.2 a while back, we decided not to
carry over our old tickets. Instead we just built a new RT with a
fresh database. But in order to avoid confusion with our ticket
history, we told RT3 to begin ticket numbering at a higher number than
that of the last RT2 ticket (i.e., we started RT3 with ticket #60000).
Now we’d like to see if we can move the RT2 tickets (we’re still
running RT2 on another machine) to RT3, preserving their old ticket
numbers (which are unused numbers in RT3).
Is there a safe way to do this? Could we, for example, temporarily
reset the ticket id auto-increment starting value from 60000 to 1,
feed the old tickets in with their original numbers, then reset the
auto-increment starting value back to 60000? Would new tickets
subsequently created start at the next available number after our
highest RT3 ticket number, or would RT get confused because it would
try to start creating new tickets with number 60001?
I have a feeling this will cause problems, but I’d like to find out
for sure.
Of course we can always move the tickets from RT2 to RT3 with newly
assigned ticket numbers, but it would be preferable for us if we can
preserve the old ticket numbers in the new RT, for tracking purposes.
(I know, we should have thought of all this at the time we upgraded!).
Thanks.
Mike
Mike Friedman System and Network Security
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
http://ack.Berkeley.EDU/~mikef http://security.berkeley.edu
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBQ/JPxa0bf1iNr4mCEQK1nACg/ksChQVEAWbolYb7Gz0G1gYwK08Ani0B
V5HZSl7IIHXhsBCOcv/OovB9
=igSW
-----END PGP SIGNATURE-----
The rt-users Archives
Be sure to check out the RT Wiki at http://wiki.bestpractical.com
Download a free sample chapter of RT Essentials from O’Reilly Media at
http://rtbook.bestpractical.com
WE’RE COMING TO YOUR TOWN SOON - RT Training in Amsterdam, Boston and
San Francisco - Find out more at
http://bestpractical.com/services/training.html
Drew Barnes
Applications Analyst
Raymond Walters College
University of Cincinnati
At Tuesday 2/14/2006 04:46 PM, Mike Friedman wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
When we moved from RT 2.0.15 to 3.4.2 a while back, we decided not to
carry over our old tickets. Instead we just built a new RT with a fresh
database. But in order to avoid confusion with our ticket history, we
told RT3 to begin ticket numbering at a higher number than that of the
last RT2 ticket (i.e., we started RT3 with ticket #60000).
Now we’d like to see if we can move the RT2 tickets (we’re still running
RT2 on another machine) to RT3, preserving their old ticket numbers
(which are unused numbers in RT3).
Is there a safe way to do this? Could we, for example, temporarily reset
the ticket id auto-increment starting value from 60000 to 1, feed the old
tickets in with their original numbers, then reset the auto-increment
starting value back to 60000? Would new tickets subsequently created
start at the next available number after our highest RT3 ticket number, or
would RT get confused because it would try to start creating new tickets
with number 60001?
How are you planning to insert the latest batch of tickets? If you use the
API to create a ticket and you supply a ticket number, I think it might be
true that your supplied value will be used, rather than an autogenned
value, but I can’t be absolutely sure about that - it’s worth a try.
Playing with the ticket ID auto-increment might not do what you want - can
you guarantee that your old tickets have IDs in an unbroken sequence
starting from 1? If there are gaps in the old ticket numbers, you’ll end up
with mismatches.
Steve