No disagreement here. There are multiple ways to achieve that behavior
(e.g. your current implementation or postpending the repo's name to the
event), I'm just suggesting what the default behavior should be, based on
our current DB schema and past experience.


On Thu, Feb 21, 2013 at 9:06 AM, Katy Huff <notifications@github.com> wrote:

> In src/Core/Utility/EventManager.h:
>
> > +    as they come.
> > +
> > +    @param count # events to buffer before flushing to backends.
> > +    */
> > +    void set_dump_count(unsigned int count);
> > +
> > +    /*!
> > +    Creates a new event for creator with title.  It uses uniquely
> > +    identifiable information from creator (e.g. ID) to create a unique
> > +    namespaces for related events.
> > +
> > +    @param creator the agent that created this event @param title a
> > +    label to distinguish event sets from other sets from the same
> > +    creator.
> > +    */
> > +    event_ptr newEvent(Model* creator, std::string title);
>
> That suggestion is fine, but I'll just point out that there is a use case.
> In Cyder, each repository should have a detailed set of tables specific
> just to it. @rwcarlsen <https://github.com/rwcarlsen> has implemented
> this interface in Cyder and it's nice to have that behavior.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/cyclus/cyclus/pull/456/files#r3099751>.
>
>