similar to: Extending finders to include a session variable as an option??

when i require acts_as_paranoid I''m getting: undefined method `alias_method_chain'' for #<Class:ActiveRecord::Base> (NoMethodError) It happens in acts_as_paranoid''s init.rb. here''s the whole file. the alias_method_chain is near the bottom. please advise. class << ActiveRecord::Base def belongs_to_with_deleted(association_id, options = {})

hello, I''m using the trunk versions of both plugins. I''m running into this error when I run a migration to try and create the versioned table for the model ''Note'' stack level too deep /Users/Adam/dev/sweetspot/app/trunk/config/../vendor/plugins/ acts_as_paranoid/init.rb:5:in `belongs_to_without_deleted''

Trying this straight from the README: I have acts_as_paranoid in my model (Course), and added the deleted_at column. This is OK: Course.find_with_deleted(:all) Course.find(:all, :with_deleted => true) gives: ArgumentError: Unknown key(s): with_deleted from /opt/local/lib/ruby/gems/1.8/gems/activesupport-2.0.2/lib/ active_support/core_ext/hash/keys.rb:49:in `assert_valid_keys''

Hi... Isn''t there a proper way or hack/workaround for the following? * For the example with unfortunate disabilities.. look below,,, Usage of has_* (associationmethods) do {def with_deleted AccociatedModel#with_scope} {Paranoid''s#find_with_deleted}... The has_one associations give me a nil object when invoking it with Model.association_OBJECT.with_deleted. Has_many does like

Here''s the full error: 1) Error: test_add_message_to_existing_ticket(TicketTest): ArgumentError: Unknown key(s): group /usr/lib/ruby/gems/1.8/gems/activesupport-1.2.4/lib/active_support/core_ext/hash/keys.rb:48:in `assert_valid_keys'' /usr/lib/ruby/gems/1.8/gems/acts_as_paranoid-0.2/lib/acts_as_paranoid.rb:125:in `validate_find_options''

Hello all, I just ran into something that I think is a bug, and I would like to confirm with the core team whether this is expected/desired behavior or if this is a bug that I should file and develop failing tests for (I doubt I have the active record method_missing fu to actually patch it). Test Scenario: I would like to find or initialize a new user and base the find on the users email

HI all, I just started using acts_as_paranoid, and I''ve been using gettext for a while. Now I get the below errors when I run rake gettext:updatepo. It''s interesting that the errors seem to stack up, so the first file just errors on belongs_to_without_deleted, the second file has a layer of eval, the second has two layers of eval, and so forth. I''ve tried for a while

Hi, I''ve run into two small problems with acts_as_paranoid and wondered if anyone else has experienced them as well (and if yes, if they have any solutions). 1. When using has_many :through, AAP doesn''t seem to take into account the fact that your join model might also be paranoid. My solution to this at the moment is to add an explicit conditions clause to the has_many

Acts_as_paranoid is giving me a headache when performing migrations. For some reason when I perform a migration I get a "stack level too deep" error. If I comment out the database inserts that are performed (countries, regions, and a base admin) it works well. Even after minimizing the data that is inserted on the migration to one record it still throws the same error. When running

Hi, I understand there are total 11 types of key Options for finding a record. The all 11 valid keys for the options hash are :conditions, :include, :order, :select, :group, :joins, :from, :limit, :offset, :readonly, and :lock. We also have Dynamic Finders for the same. e.g. ... find_by etc... I would like to know, how many types of dynamic finders, Active Record provides, to match all those

I can not seem to make finders work with aliases. My goal is to map some fugly field names to nice field names and have the finders work with the nice field names. An example. class Users < ActiveRecord::Base alias :password :UserPWD end This doesn''t seem to work because obviously the object doesn''t have a method called UserPWD. What is the best way (short of a view) to

Hi all, I am not certain this is a 1.8.4 related issue, but I think it might be. I''m trying to use dynamic finders for my Category and Post models, such that a request /blog/categories/general would detect the slug and do a find_by_slug() instead of find(params[:id]). My have_slug?() method works fine, and the dynamic finders *were* working fine until I moved it off my local machine

Hello, I posted this on the rails talk group but received no response. Perhaps someone on this list could weigh in on whether this is expected/desired behavior or a bug that I should file and develop failing tests for (I doubt I have the active record method_missing fu to actually patch it). Test Scenario: I would like to find or initialize a new user and base the find on the users email

I have some finders in my models where I write some of the sql myself. I of course want to test these, but am not sure the best way. Should I just let them roll through to the db, and verify they return the correct objects based on the fixtures I load, or should I spec the actual query? I know that DB access is sort of frowned upon, but is this a situation where it is more or less acceptable? My

Hello everyone, I have another question related to a legacy schema I am working with. Do dynamic finders work with legacy schemas in general? The schema I am working with uses hungarian prefixes for column names. For example fOpen is 0 if a bug is closed and 1 if it is open (type smallint). When I try @bugs = Bug.find_all_by_fOpen(1), I get the following exception: undefined method

Hi All! It''s been a while since I had to ask for help, but I''m back! I''ve finished beta testing my big app and started the transition to production. Everything went fine and the production version was working till I was asked to add another model :-( (Almost a year of beta testing and they only come up with it after moving to production :-D ) I successfully

When I use find_by_name method I get LIMIT 1 result. > SELECT "users".* FROM "users" WHERE "users"."age" = 25 LIMIT 1 But the "age" column is not unique in my table and its value may repeat. So I expect that an array of records where "age" is 25 will be returned. But AR limits the query by 1. How to avoid it? Or is it the default

I have these 3 models. class Ivr < ActiveRecord::Base has_many :klusterings, :dependent => :destroy has_many :klusters, :through => :klusterings, :uniq => true end class Kluster < ActiveRecord::Base has_many :klusterings, :dependent => :destroy has_many :ivrs, :through => :klusterings, :uniq => true end class Klustering < ActiveRecord::Base belongs_to :kluster

Hi Renato, Currently I am building a set of patches which will add AAP piece-wise. I'm following the approach that AVR (and now RISC-V), and the patches I plan on adding are as follows: * Target triple * ELF definition * Basic skeleton with the required build system changes (targetinfo + target machine) * Instruction + Register tablegen * MC layer support * AsmParser * InstPrinter *

Hi All, So I thought I had this acts_as_paranoid problem previously and fixed by going to rails 0.14.2, although I''m not 100% it was the same thing. I''m now on rails 0.14.3 and I''m getting: undefined method `constrain'' for class `Class'' for any model that includes acts_as_paranoid. My application trace is below. Has anyone else got this and know a