Forum: Ferret Ferret Trampling Namespace

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
9b96e0c57eccef0f495b837b714fc466?d=identicon&s=25 Fraumeni, James (Guest)
on 2006-02-10 23:01
(Received via mailing list)
Greetings. Apologies if I missed something like this in the archives or
internet, but I'm having issues using Ferret with Rails. Specifically, I
have a class class "Weight" in my application (it happens to be a
model). My app runs perfectly fine until it first executes "require
'ferret'". At that point, my definition of the class "Weight" disappears
and I get "uninitialized constant Weight" errors. I see that Ferret also
has a Weight class (Ferret::Search::Weight) so I assume that Ferret
isn't playing nicely with namespaces, although I assume that it's caused
by some interaction between Rails and Ferret as it does not occurr in
IRB.
	Has anyone else come across an issue of Ferret trampling namespace? I
have tried putting the indexing code in a number of places within my
app, and "load"ing Ferret rather then "require"ing it, but loading tends
to fail to load Ferret.
	Thanks for any insight. I am a Ruby and Rails nuby and am using Win32
(temporarilly), Ruby 1.8.2, Ferret 0.3.2, and Rails 1.0.0.

					James

--
James Fraumeni
Center for the Evaluation of Value and Risk in Health
Institute for Clinical Research and Health Policy Studies
750 Washington St.
Tufts-New England Medical Center, #063
Boston, MA 02111
(617) 636-2577
jfraumeni@tufts-nemc.org



**********************
Confidentiality Notice
**********************
     The information transmitted in this e-mail is intended only for the
person or entity to which it is addressed and may contain confidential
and/or privileged information.  Any review, retransmission,
dissemination or other use of or taking of any action in reliance upon
this information by persons or entities other than the intended
recipient is prohibited.
     If you received this e-mail in error, please contact the sender and
delete the e-mail and any attached material immediately.  Thank you.
This topic is locked and can not be replied to.