Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I know this doesn't address the error you're getting, but I'd suggest using three one-to-many relationships instead of one many-to-many relationship.</p> <p>The conventional purpose of <code>has_many :through =&gt; ...</code> (many-to-many) is for when you have something like <code>students</code> and <code>classes</code>. A student can be in <strong>any</strong> number of classes. A class can have <strong>any</strong> number of students. Totally arbitrary numbers on both sides of the relationship.</p> <p>But that isn't your situation here. Your projects can be in exactly one main category, one optional category 1, and one optional category 2. It's a totally different problem and it isn't the problem that <code>has_many :through</code> is designed to solve.</p> <p>I suggest this arrangement:</p> <pre><code>class Project &lt; ActiveRecord::Base belongs_to :main_category, :class_name =&gt; "Category", :foreign_key =&gt; 'main_category_id' belongs_to :optional_category_1, :class_name =&gt; "Category", :foreign_key =&gt; 'optional_category_1_id' belongs_to :optional_category_2, :class_name =&gt; "Category", :foreign_key =&gt; 'optional_category_2_id' end class Category &lt; ActiveRecord::Base has_many :main_category_projects, :class_name =&gt; "Project", :foreign_key =&gt; 'main_category_id' has_many :optional_category_1_projects, :class_name =&gt; "Project", :foreign_key =&gt; 'optional_category_1_id' has_many :optional_category_2_projects, :class_name =&gt; "Project", :foreign_key =&gt; 'optional_category_2_id' end </code></pre> <p>Then you'll be able to do stuff like:</p> <pre><code>my_project.main_category my_category.optional_category_1_projects # etc... </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POhas_many through update issue
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USEthan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POhas_many through update issue
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COExcellent. I have never quite understood has_many through well enough. Part of the problem with this issue is that it is from a legacy database, where changing the structure may not be possible, without reworking a lot of other things. But this is a good suggestion, and I will try and see if I can do it. I wish I could figure out why my solution is not working, as it seems to be valid within the parameters of has_many through.
      singulars
      1. PO
      1. USVikram Goyal
 

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