search for: property_types

Hey All, I have two tables.. One belongs to another. Why can''t I reference table1.table2.attribute? Specifically, using scaffolding: property.rb - has_one :PropertyType property_type.rb - has_many :Properties property_controller - def list @property_pages, @properties = paginate :properties, :per_page => 10 end list.html: 1. <% for property in @properties %> 2.

Steve - That was the issue.. It seems obvious now, but I needed to reference Property.PropertType.name instead of property.propertytype.name Thanks!! Brian -----Original Message----- From: rails-bounces@lists.rubyonrails.org [mailto:rails-bounces@lists.rubyonrails.org] On Behalf Of Steve Koppelman Sent: Wednesday, March 08, 2006 5:00 PM To: rails@lists.rubyonrails.org Subject: [Rails] Re:

I''m trying to create a dropdown list that''s populated from a model but which has the 2nd item in the model as the default selection. This is possible. Here''s the model snippet. PROPERTY_TYPES = [[''Choose'', ''''], [''Residential'', ''Residential''], [''Commercial'', ''Commercial'']] Here''s the form snippet <%= f.select...

I''m running into the need (on at least one project now) to implement end-user-customizable "metadata" or properties on model objects. The standard example would be a Person class that had first_name, last_name, etc. but would need to be extended real-time (through the web admin interface) with properties such as phone_number : varchar (30). I''ve done some basic

Hey guys, Now that the Lucy[1] project has Apache approval and is about to begin, the onus is no longer on Ferret to strive for Lucene compatability. (We''ll be doing that in Lucy). So I''m starting to think about ways to improve Ferret''s API. The first part that needs to be improved is the Document API. It''s annoying having to type all the attributes to