[Rt-devel] multiple primary keys?

[Jim Meyer]

Hello!

On 6/28/06, Josh England <jjengla at sandia.gov> wrote:
> On Wed, 2006-06-28 at 20:16 -0400, Todd Chapman wrote:
> > A little of the subject, but why not use a Ticket or Asset to
> > store your events?
>
> I'm looking to use RT with AT along with some stuff for tracking events
> (ET?) to track system events often *related* to assets and only create
> tickets for assets that need to be serviced.  Events just seem to me to
> be a different beast, similar to tickets, but not really the same.
>
> Tickets and Assets are functionally different and a little too
> heavyweight for the number of events I might need to process.  It takes
> over 2 hours to add 4500 assets (with custom fields) to the database.
> So far, with a lightweight Event object (with no custom fields), I'm
> adding 862 events/sec.  I haven't timed ticket creation, but I might
> look at that tomorrow.

Perhaps you should be using creating RT::Transactions for your events?
Much less heavyweight, already have the concept of relating to Tickets
(and probably Assets, though I've not looked at Todd's AT extension).
I haven't tried creating transactions without a ticket, but in my
admittedly fuzzy recollection of the code it seems tractable.

Good luck!

--j
-- 
Jim Meyer, Geek at Large                                    purp at acm.org