All the classes inside 'models' folder are considered as ActiveRecord
classes and Rails will try to find a corresponding table in the
database named as plural of the model. It's a convention; To bypass it
and have a model independent from ActiveRecord class, create it in
'lib' folder and require it in the class where you need it.

On Feb 25, 8:38 am, Jeff Miller <li...@ruby-forum.com> wrote:
> Hello everyone,
>   I'm working on a Rails 3 social networking app (following RailsSpace
> by Addison Wesley) but the book is old and using Rails 2. Thus far I've
> been chugging along converting it along the way, but I'm running into
> some trouble with my Avatar model. I'm trying to implement it without
> having a table in the database. In accordance to the book, I created the
> model manually (instead of with generate) and add an initialize
> function. I created the corresponding controller and views, but when I
> try to upload my avatar, it errors out telling me that database.avatars
> doesn't exist.
>
> I'm pretty sure I've got the controller and model right, but I just need
> to tell Rails to NOT look in the database for this model...
>
> Any ideas?
>
> Thanks in advance,
>   - Jeff
>
> --
> Posted viahttp://www.ruby-forum.com/.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en.

Reply via email to