J
Jean-Marc Molina
Hello,
I found an interesting ER diagram on the "Module:
ActiveRecord::Associations::ClassMethods" page of the Rails Framework
Documentation :
http://ar.rubyonrails.org/classes/ActiveRecord/Associations/ClassMethods.html.
At the beginning we can read « Associations are a set of macro-like class
methods for tying objects together through foreign keys. They express
relationships like "Project has one Project Manager" or "Project belongs to
a Portfolio". ». I would like to learn more about that concept of expressing
relationships between objects. I only knew it as a design concept and can't
remember seeing it applied "as this" in the source code using macros. I find
the idea interesting. Is it some kind of Ruby "Best Practices" or
design/development pattern ?
JM.
PS : Note that the diagram is not displayed on the "official" page :
http://api.rubyonrails.org/classes/ActiveRecord/Associations/ClassMethods.html. I was only able to find it on that "mirror".
I found an interesting ER diagram on the "Module:
ActiveRecord::Associations::ClassMethods" page of the Rails Framework
Documentation :
http://ar.rubyonrails.org/classes/ActiveRecord/Associations/ClassMethods.html.
At the beginning we can read « Associations are a set of macro-like class
methods for tying objects together through foreign keys. They express
relationships like "Project has one Project Manager" or "Project belongs to
a Portfolio". ». I would like to learn more about that concept of expressing
relationships between objects. I only knew it as a design concept and can't
remember seeing it applied "as this" in the source code using macros. I find
the idea interesting. Is it some kind of Ruby "Best Practices" or
design/development pattern ?
JM.
PS : Note that the diagram is not displayed on the "official" page :
http://api.rubyonrails.org/classes/ActiveRecord/Associations/ClassMethods.html. I was only able to find it on that "mirror".