Fwd: [Nitro] Not expected behavior
george.moschovitis at gmail.com
Sat Mar 19 01:20:09 EST 2005
---------- Forwarded message ----------
From: George Moschovitis <george.moschovitis at gmail.com>
Date: Sat, 19 Mar 2005 08:02:41 +0200
Subject: Re: [Nitro] Not expected behavior
To: james_b at neurogami.com
you are correct, Og only automatically finds manageable classes that
are already defined. Alternatively you can call:
og = OgDatabase.new(...)
to explicitly manage classes.
I 'll ad a new method like
og.find_manageable_classes (or something like this, any idea for a better name?)
Even better, if you have any other idea, how I could recode this to
work as expected, please let me know!
for any other problems, dont hesitate to contact me.
ps: I am working on a relly cool feature. The nested intervals sql
tree traversal pattern, available with just one macron :)
On Fri, 18 Mar 2005 22:09:40 -0700, James Britt
<jamesUNDERBARb at neurogami.com> wrote:
> I discovered (though perhaps this is documented someplace and it eluded
> my conscious brain) that you apparently have to call the Og database
> configuration AFTER you have defined the classes you plan on persisting.
> I noticed that my code differed from the tutorial example in that I put
> the db config part up top; this just seems more natural, putting config
> details first.
> When I moved them *after* my class code, though, it magically worked.
> Not sure I like this. It seems that it would restrict how and where one
> defines configuration details. In all likelihood, I would use a
> 'require' call to pull in config details, so the class ode would always
> come after the parsing of the class defs. I gather the enchant code
> only knows to enchant classes already in object space?
> Is this intentional, or a coincidence?
> Nitro-general mailing list
> Nitro-general at rubyforge.org
More information about the Nitro-general