[Tracker-discuss] Need some help - how do I get my auditor to run for each submission?

["Martin v. Löwis"]

> Thanks.  Shouldn't this be clearly documented somewhere? 

isn't it clearly explained here:?

http://roundup.sourceforge.net/doc-0.8/design.html#detector-interface

> What's the difference between issue and msg?

They have different classes. Classes are explained here:

http://roundup.sourceforge.net/doc-0.8/design.html#items-and-classes

> Web submission vs. email?

I believe they are different only from a security point of view;
for detectors, there will be no difference.

> Is there one choke point where I can execute the auditor?

This question I do not understand. What's a choke point?

The auditors are invoked whenever an item is created or
modified.

> Where do web and email submissions coincide? 

For the detector, they are the same.

> I'm unable to actually create a database interactively.  The
> example session in the Application Example section of design.txt clearly
> doesn't work.

That's no surprise if you tried to execute it literally - there won't
be a foo.db database unless you create it. In the python-dev tracker,
the database is assumed to be a postgres one, and its name is assumed
to be "roundup". See

http://wiki.python.org/moin/TrackerDevelopment

> I poked around a bit and tried creating a
> back_anydbm.Database.  That also failed.  If Database objects are supposed
> to have issue attributes I ought to be able to find "self.issue" somewhere
> in the Roundup code but have not been able to.

It's not hard-coded in round-up that there always is an issue class.
Instead, the database schema is defined in python-dev/schema.py.

> Again, what's the difference between "msg" and "issue"?  Can I read about
> any of this anywhere?

Read about classes, and about the database schema.

Regards,
Martin