Rails - May 2009 - model

Hi,

Should every model have an associated table in database? I have a model
as a subclass of another model class. I am getting ''MySQL gone
away''
error while creating a new object of this subclass.

Any clues?

-
Amita.
-- 
Posted via http://www.ruby-forum.com/.

On May 1, 7:09 am, Amita Bhatkhande
<rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:
> Hi,
>
> Should every model have an associated table in database? I have a model
> as a subclass of another model class.

not necessarily. For example when using single table inheritance then
a model and its subclasses will share a table, and you can of course
have non-activerecord model classes that don;t use the database at
all.

Fred
>I am getting ''MySQL gone away''
> error while creating a new object of this subclass.
>
> Any clues?
>
> -
> Amita.
> --
> Posted viahttp://www.ruby-forum.com/.

> I am getting ''MySQL gone away''
> error while creating a new object of this subclass.
Refactor the common code between your tabled and table-less *models into a 
module, and let both models include that module.

*yes, it''s still a model, even if it has no DB persistence.

-- 
   Phlip
   http://flea.sourceforge.net/resume.html