similar to: ActiveRecord associations -- when to use force_reload = true

I have the following associations. class Document < ActiveRecord::Base has_many :document_sections, :dependent => :destroy, :autosave => true has_many :document_items, :through => :document_sections end class DocumentSection < ActiveRecord::Base belongs_to :document has_many :document_items, :dependent => :destroy, :autosave => true end class DocumentItem <

Given the models Country, State, City and Person as follows. class Country < ActiveRecord::Base has_many :states end class State < ActiveRecord::Base belongs_to :country has_many :cities end class City < ActiveRecord::Base belongs_to :state has_many :people end class Person < ActiveRecord::Base belongs_to :city end Is there any way that doesn''t allow to delete

A while back, I had some doubts on the use of associations. I still haven''t got a satisfactory guidance so that I can spring ahead with the project. I am trying to understand from a ruby point of view on doing things. Basically I have a controller that gives me a list of students. And each student may have say home address and mailing address. Hence I can model as shown below. How do I

Is there some sort of good pattern for dealing with computed values with Rails/ActiveRecord? A simple example: 3 tables, classes, students, and student_class_records (habtm style relation but contains a good deal of additional state so is modeled explicitly) Something like select the 10 classes with the most students. Easy enough in SQL. So I''m using a lot of find_by_sql and

Considering an object with several has_many :through => associations, what is the ''best'' way to handle validations? As an example: class Student < ActiveRecord::Base # some attrbutes like # :name # :grade # relationships has_many :students_assignment, :dependent => :destroy has_many :assignments, :through => :students_assignment has_many

Hi list, how are ya? So, my current project is just begging for the ability to have parameterized associations in my ActiveRecord classes. Basically I need something that is a cross between named scopes and standard associations (has_many specifically). I''m wondering if such a thing exists or, if not, if anyone else has an elegant, equivalent solution? Example: class Sprocket <

I''d like to organise my active records into modules but can''t get the associations to work. The doc says that associations within the same module should work. I''ve tried using the class_name option too but still doesn''t work. Can anyone help? For example module Mod1 class Animal < ActiveRecord::Base has_many :dogs, :class_name =>

How do I write a test which proves something like "Post :has_many Comments" and "Comment :belongs_to Post"? It doesn''t seem to be covered in "A Guide to Testing the Rails" on manuals.rubyonrails.com. Cheers, Robert. -- Posted via http://www.ruby-forum.com/.

Hi everyone, I have the following classes: class User < ActiveRecord::Base devise :database_authenticatable, :registerable, :timeoutable, :recoverable, :rememberable, :trackable, :validatable has_many :comments, :dependent => destroy ... end class Comment < ActiveRecord::Base belongs_to :user belongs_to :commentable, :polymorphic => true ... end In rails console,

Hello, I have a Company that has_and_belongs_to_many Persons. A Person has_many Emails. I want to display each Person''s Email for each Company, so I try this: companies = Company.find(:all) for company in companies persons = company.persons for person in persons puts person.email end end Unfortunately, this doesn''t work correctly. Let''s say the id of

First of all, I love Ruby on Rails. I have an intermediate understanding of PHP, JavaScript, DOM and CSS, and that''s the extent of my programming experience. I''m developing an online game''s web presence with another colleague. We''re the only two technical guys on a team of +10 content developers. So, baring all that in mind, here are my questions with a

Can someone clarify this for me? Suppose I have two tables like: class Company < ActiveRecord::Base belongs_to :category end class Category < ActiveRecord::Base has_many :companies end I understand that the belongs_to causes related companies to be read from the db when I ask for a category. I suspect SQL something like select * from categories, companies where category.id

Is there anyway to refer to the entities being linked in a foreign key field of a fixture by name instead of id? Ie, if I have categories.yml some_cat: id: 1 name: Foo other_cat: id: 2 name: Bar data.yml some_item: id: 1 category_id: <%= categories(:some_cat).id %> name: Hello World The above doesn''t work due to scope, even if the fixtures are loaded in the proper

So I want to SELECT from multiple tables, so as to be able to do "SELECT FROM foo, bar WHERE foo.id=bar.id AND bar.baz=23". How do I do it with AR#find? Also, I need this for associations. has_many et. al. have :finder_sql, which is nice, but feels like a Pyrrhic: it''s basically doing the association in pure SQL, defeating the purpose of AR. -- -Alder

Hi, Does anyone know a good way to override AR associations to take special cases into account. My current take is the example below which allows the ''root'' user to access all products, but only works if I remember to call it with a .all/.find or similar method: ''user.products.all'' instead of ''user.products''. Ideally I guess I want to return a

I want to find out what are the associations with another active record class. So If my class is as below: Class Component < ActiveRecord::Base has_many :branches end class Branch < ActiveRecord::Base belongs_to :component end and then I do Component.reflections[:branches].active_record I would expect that to be Branch but it is in fact Component. The inspection of

One problem with the daylight savings is that they mess with reporting tools that use timestamps. I guess an application could be configured to log UTC instead of local time, but that's not always doable. Also, if you have servers in several different timezones, it's better if all systems follow the same clock. So, I'm thinking it's perhaps better if I just use

Looking for some guidance/support on what feels like might not be an uncommon use-case. `User.has_many accounts` `User.has_many payment_methods` `Account.belongs_to :user` `Account.belongs_to :payment_method` `PaymentMethod.has_many :accounts` There are lots of `Accounts`. When I (a `User`) want to assign accounts to a `PaymentMethod`, I really don''t want to scope against all of them,

hi, I found a bug in ActiveRecord association SQL INNER JOIN codes. in has_many, has_one, habtm and belongs_to queries the foreign key is determined from the table name of reflection and self. but that''s worng because if you use a global prefix or suffix for your tables the foreign keys will be in format of PREFIX_CLASSNAME_SUFFIX_id which is wrong, because it breaks the advantage of

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