[Nitro] Og:Exception, Og::Deleted

[Brian Davis]

On Tue, 13 Mar 2007 16:55:54 -0700
"Judson Lester" <nyarly at gmail.com> wrote:

> Most of everything goes through lib/store/sql.rb
> 
> Individual DB types are supported by lib/adaptor/<db>.rb which
> includes a descendant of SqlStore
> 
> If you want to understand Og pretty thoroughly, follow the process of
> enchanting a class.  Why it happens, when it happens and what happens.
>  Hint: it starts in og/ann_attr.rb and continues into og/manager.rb.
> 
> That should get you up to speed pretty quickly.
> 
> On 3/13/07, Brian Davis <brian.william.davis at gmail.com> wrote:
> > On Tue, 13 Mar 2007 16:34:56 -0700
> > "Judson Lester" <nyarly at gmail.com> wrote:
> >
> > > It's on my list.  I've got a bunch of things I'd like to do to the
> > > code, but my ethic is such that I don't want to add more failing
> > > specs.  Your failing spec is one of 15, and I want to see it fixed
> > > before I move on to other things.
> > >
> > > Judson
> > >
> > > On 3/13/07, Brian Davis <brian.william.davis at gmail.com> wrote:
> > > > On Tue, 13 Mar 2007 15:53:15 -0700
> > > > "Judson Lester" <nyarly at gmail.com> wrote:
> > > >
> > > > > Created a spec on Model that required the creation of
> > > > > Og::Exception < ::Exception, Og::Deleted < Exception and some
> > > > > code being added to SqlStore
> > > > >
> > > > > Judson
> > > > >
> > > >
> > > > If you could also take a look at the spec I sent in, I'd really
> > > > appreciate it (the many_to_many spec). From my cursory glance
> > > > at the internals, it looks like my proposed solution would
> > > > require wrenching out a lot of the table-naming code and the
> > > > mechanisms for fetching objects, so I was hoping for a little
> > > > guidance and counsel before breaking everything :)
> > > >
> > > > Thanks,
> > > >
> > > > Brian aka MonoDelDiablo
> > > >
> > > > --
> > > > Brian Davis
> > > >
> > > > Project Manager
> > > > FreezeCrowd, Inc.
> > > > _______________________________________________
> > > > Nitro-general mailing list
> > > > Nitro-general at rubyforge.org
> > > > http://rubyforge.org/mailman/listinfo/nitro-general
> > > >
> > >
> > >
> >
> > Of course! Take your time. I didn't mean to push. Personally, I'd
> > like to slay the beast myself, but I don't have much free time this
> > month. Any pointers on architecture you could shoot my way would go
> > a long way toward me reducing your workload by taking on my spec
> > myself.
> >
> > Whatever happens, I appreciate all the work you're putting in and
> > look forward to helping where I may.
> >
> > Brian aka MonoDelDiablo
> >
> > --
> > Brian Davis
> >
> > Project Manager
> > FreezeCrowd, Inc.
> > _______________________________________________
> > Nitro-general mailing list
> > Nitro-general at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/nitro-general
> >
> 
> 

Thanks a bunch! I had started backwards; from the SQL-specific logic.
Whenever I get a chance to sit down and really study things, you can
count on a few patches (from what I saw of most of the low-level code,
all table names are assumed to be comprised of class names... so I'll
have to mess creatively deal with that assumption and think up a
"better" method of naming that won't break Oracle). 

Brian aka MonoDelDiablo

-- 
Brian Davis

Project Manager
FreezeCrowd, Inc.