Re: Re: Attributes in classes db/migrate or app/models

Hassan Schroeder
2012-07-21T15:34:27Z

On Sat, Jul 21, 2012 at 8:20 AM, Cortomix aa
<lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote:

> I explain my problem. If I''ve got a  Person class in my model,
with
> Rails I will have a class CreatePersons (for example) in db/migrate/
> with its attributes (name, address, telephone...)

Which is only used to create the database table, and which may be
overridden by later migrations. Once used, it''s meaningless, other
than documenting the history of development.

> class Persona < ActiveRecord::Base
> end

> If I work with the Person class, I will have a class without attributes
> name or address!!

The class has those attributes; what makes you think it doesn''t? It
just isn''t necessary for them to be written in the file that defines
the
class for them to exist; ActiveRecord derives them from the schema
of the database.

Open up a console session and play with it.
>> person = Person.new
>> person.name= "Bob"
>> person.name
=>  "Bob"

Create a non-AR class and experiment with it. Learning through
interactive exploring is one of the advantages of Ruby over Java :-)

--
Hassan Schroeder ------------------------
hassan.schroeder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
http://about.me/hassanschroeder
twitter: @hassan