search for: property_name

...arkable has_one :value, :as => :markable end ? Based on what I know of the underlying implementation, this looks impossible. One alternative is to declare artificial classes PropertyName and PropertyValue, each of which has_one :value, :as => markable and then change Property to has_one :property_name and has_one :property_value: class PropertyName < ActiveRecord::Base has_one :value, :as => :markable end class PropertyValue < ActiveRecord::Base has_one :value, :as => :markable end class Property < ActiveRecord::Base has_one :property_name has_one :property_value end...

[PATCH 1/3] kms: Don't hardcode the output properties [PATCH 2/3] kms: Implement output->get_property when RandR1.3 is available. [PATCH 3/3] kms: Add TV-out support src/drmmode_display.c | 403 ++++++++++++++++++++++++++++++++----------------- 1 files changed, 261 insertions(+), 142 deletions(-)

...oing to try to implement something myself. Hopefully, this can be released to the community if it works. Here''s the basic concept as I see it: CREATE TABLE property( id int not null primary key auto_increment, ar_class varchar(255), -- AR class this property extends property_name varchar(255), property_type text -- MySQL or Ruby type ); CREATE TABLE property_value( id int not null primary key auto_increment, foreign_id int not null, -- PK of the referenced object property_id int not null, -- Property has_many :property_values, Property...

...roperty }, :loading => ''Form.disable("property-form")'', :complete => ''Form.enable("property-form")'', :html => { :id => ''property-form'' } do |f| %> ..... <div> <label class="label" for="property_name">Property Name</label><br /> <%= f.text_field ''name'', :size => 30 %><br /> </div> .... thanks for any trick Kad -- Posted via http://www.ruby-forum.com/.

Hi all I''m using a_a_f in rails with a StemmingAnalyzer, in the index and in my search. I got the idea from this topic: http://www.ruby-forum.com/topic/80178 I''m having a problem with some search terms - i narrowed one of them down to the inclusion of the word ''fly''. Can anyone give me any clues at to what might be happening, or even how i can investigate?

Hi, here i describe my problem: mi application must allow 2 basic issues: first: the users may be able to create ''people'' (this would be a model with a scaffold, and is not an issue, the problem comes with requierement #2) second: the users should be able to add new fields to that model, for example: the model ''person'' may have 2 fields, let say:

I''ve been struggling a bit trying to figure out the best way to design/implement a system with authentication/authorization, and was hoping some of you may be able to offer some advice.. At the moment, I have a system with 4 different types of users - clients, administrators, sales_reps, and public_users. I''m using "Authorizing Users with Roles" from the Rails Recipes