Databases
StackOverflow2013
Postsdbo
POSomething seems to be broken in my belongs_to, has_one relationship
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSomething seems to be broken in my belongs_to, has_one relationship
    primarykey
    data
    text
    <p>I have a data model that looks like this:</p> <p>A <code>customer</code> has <code>subscription_id</code> and <code>setup_id</code> as parameters. In some cases, <code>customer</code> will only have one of the parameters. In other cases, it will have both. </p> <p>Currently, if I make a new customer through either the subscriptions flow or the setups flow, either <code>Subscription.last</code> or <code>Setup.last</code> will reflect the most recent customer that was created (with <code>customer_id</code> equalling the last customer created)</p> <p>However, I am having the problem of <code>Customer.setup_id</code> or <code>Custumer.subscription_id</code> being nil in all cases.</p> <p>Here's my code from both <code>subscription.rb</code> and <code>setup.rb</code>:</p> <pre><code>class Subscription &lt; ActiveRecord::Base attr_accessible :status, :customer_id belongs_to :customer end class Setup &lt; ActiveRecord::Base attr_accessible :status, :customer_id belongs_to :customer end </code></pre> <p>And in <code>customer.rb</code>:</p> <pre><code>class Customer &lt; ActiveRecord::Base attr_accessible :email, :name, :stripe_token, :subscription_id, :setup_id, :phone, :plan has_one :subscription has_one :setup end </code></pre> <p>I'm not sure what I'm doing incorrectly here but I'd love it if the three data models could talk to each other correctly.</p> <p><strong>Edit</strong>: Is it bad that both <code>setup</code> and <code>subscription</code> belong to <code>:user</code> rather than <code>:customer</code>?</p> <p><strong>Edit 2</strong>: Updated the code of setup.rb and subscriptions.rb to correctly reflect the data model currently. And <code>customer.rb</code> is still not recognizing the correct <code>setup_id</code> or <code>subscription_id</code></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USZack Shapiro
    1. USZack Shapiro
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI'm not seeing the has_many. You're trying to set up two belongs_to relationships. If it really is a 1 to 1 based on a foreign key, you should use has_one (and your sub and setup models would have no user_id). As to the edit: yes, it is bad.
      singulars
      1. POSomething seems to be broken in my belongs_to, has_one relationship
      1. USnumbers1311407
    2. CO@numbers1311407 My title was incorrect. The `customer` model has two has_one relationships. Should I change the belongs_to to :customer?
      singulars
      1. POSomething seems to be broken in my belongs_to, has_one relationship
      1. USZack Shapiro
    3. COYes. Each association needs two declarations - one for each side of the association.
      singulars
      1. POSomething seems to be broken in my belongs_to, has_one relationship
      1. USCameron Martin
 

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