Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Okay, after the lengthy discussion in the comments, this is what I believe you need:</p> <pre><code># app/models/user.rb class User &lt; ActiveRecord::Base # Include default devise modules. Others available are: # :token_authenticatable, :confirmable, :lockable and :timeoutable # Setup accessible (or protected) attributes attr_accessible :email, :password, :password_confirmation, :remember_me devise :database_authenticatable, :registerable, :recoverable, :rememberable, :trackable, :validatable, :timeoutable # You'll need to add a new column to your users table, called `company_id` belongs_to :company end # app/models/company.rb class Company &lt; ActiveRecord::Base # has_many should _always_ be a pluralised version of the class you're associating. This way, you # don't need to explicitly specify the class/foreign_keys has_many :products # Also, you may as well link back to your Users has_many :users end # app/models/product.rb class Product &lt; ActiveRecord::Base belongs_to :company validates :brand, :presence =&gt; true end # app/controllers/products_controller.rb def create # and now, to associate the product with the company, all you need to do is this: @product = current_user.company.products.build(params[:product]) if @product.save # redirect else # render and show errors end end </code></pre> <p>Rails relies <em>heavily</em> on convention. You really, <em>really</em> should follow them to make your life easier.</p> <p>Instead of your manual linking of <code>User</code> and <code>Company</code>, I've suggested that you use a proper association.</p> <p>That way, inside your Controller, all you need to do is call <code>current_user.company</code> to get the company, then use the <code>build</code> method on the association, and Rails will automatically handle assigning foreign keys.</p>
    singulars
    1. This table or related slice is empty.
    1. POforeign_key is always 1
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDan Cheail
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis answer is correct. I personally prefer to construct this type of relationship using `@product = Product.new(params[:product]); @product.company=current_user.company; @product.save`, but the method shown above will work exactly the same way.
      singulars
      1. PO
      1. USAndrew
 

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