Databases
StackOverflow2013
Postsdbo
POModel a person-to-person relationship in Ruby-on-Rails using has_many :through
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POModel a person-to-person relationship in Ruby-on-Rails using has_many :through
    primarykey
    data
    text
    <p>I would like to model a person's relationship to another person, where the relationship isn't necessarily hierarchical (i.e. friends &amp; colleagues, rather than parent &amp; children) and I am interested in capturing more detail about each relationship (e.g. notes, type of relationship, date established). Finally, I would like to use the act_as_tree relationship to be able to navigate/diagram these relationships.</p> <p>The migrations:</p> <pre><code>class CreateProfiles &lt; ActiveRecord::Migration def self.up create_table :profiles do |table| table.column :firstName, :string table.column :lastName, :string table.column :telephone, :string table.column :emailAddress, :string table.column :location, :string table.timestamps end end def self.down drop_table :profiles end end class Relationship &lt; ActiveRecord::Migration def self.up create_table :relationships, :id =&gt; false do |table| table.column my_id :integer table.column your_id :integer table.column relationshipType :string table.column dateEstablished :date table.column notes :text table.timestamps end end def self.down drop_table :relationships end end </code></pre> <p>The models:</p> <pre><code>class Person &lt; ActiveRecord::Base has_many :relationships, :foreign_key =&gt; "my_id" has_many :persons :through =&gt; :relationships end class Relationship &lt; ActiveRecord::Base belongs_to :persons acts_as_tree end </code></pre> <p>Questions:</p> <ol> <li>How do I define the relationships between these tables correctly?</li> <li>As the my_id/your_id combination is unique, does it make sense to eliminate the :id on the relationships table?</li> <li>Are there better names for the 'my_id' &amp; 'your_id' fields to make use of RoR's conventions?</li> <li>Will I have difficulties with the act_as_tree relationship if one of the columns isn't name 'parent_id'?</li> </ol>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UScraig
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POModel a person-to-person relationship in Ruby-on-Rails using has_many :through
      1. USkafuchau
      1. VTFavorite
    2. VO
      singulars
      1. POModel a person-to-person relationship in Ruby-on-Rails using has_many :through
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POModel a person-to-person relationship in Ruby-on-Rails using has_many :through
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload