[rt-devel] RT::Transaction and migration

Jesse Vincent jesse at bestpractical.com
Thu May 2 15:14:00 EDT 2002

Ideally, we'd have an RT::Transaction::Import() method. In the meantime,
well, it's a case of "if you do this, you're responsible for a lot of
integrity checking ,etc" which is why the docs tell you not to do it.

import-1.0-to-2.0 is a reasonable template for moving from 
a crufty, hacky, poorly designed ticketing system to RT2. ;)

On Thu, May 02, 2002 at 02:45:00PM -0400, Rich Lafferty wrote:
> I need to migrate from our homegrown ticketing system to RT. The
> general model is similar -- a table of tickets, and then a table of
> email messages or log entries each associated with a ticket.
> Migrating the table of tickets is straightforward, but I'm having a
> hard time getting my brane around the log entries. I see that
> import-1.0-to-2.0 calls RT::Transaction::Create() directly, but
> I also see that the documentation for RT::Transaction::Create() notes
> that it should never be used directly, but should only be accessed via
> the published RT::Ticket API.
> Is that just an RT-migration-specific bit in import-1.0-to-2.0, or
> should I use it as an example?
>   -Rich
> -- 
> Rich Lafferty --------------+-----------------------------------------------
>  Ottawa, Ontario, Canada    |  Save the Pacific Northwest Tree Octopus!
>  http://www.lafferty.ca/    |    http://zapatopi.net/treeoctopus.html
> rich at lafferty.ca -----------+-----------------------------------------------
> _______________________________________________
> rt-devel mailing list
> rt-devel at lists.fsck.com
> http://lists.fsck.com/mailman/listinfo/rt-devel

http://www.bestpractical.com/products/rt  -- Trouble Ticketing. Free.

More information about the Rt-devel mailing list