similar to: Auditing mixin for model classes. Small problem

I can''t seem to get a model observer to work. In my environment.rb I have: config.active_record.observers = :item_observer In item_observer.rb I have: class ItemObserver < ActiveRecord::Observer observe Item def after_update(item) if @old.active != item.active logger.debug ''observer#after_update'' #... end @old = nil end def

Hey guys, I''m having a hard time w/ the after_update callback on rails... As far as I can tell, when I define a after_update callback on a model, the attributes of the object have the same values that they had *before* Base.save was called. I''m probably wrong so here''s the code: UNIT TEST: def test_register_item_adjusts_account_balance account =

I have this situation where in an after_update, I would like to know the previous value of the record instead of simply being notified the record has been updated. For example let''s say I had a table called ''foo'' which had a field ''new_flag''. I want to know when the ''new_flag'' field changes from 0 -- > 1 in an after_update so I

Hi! Definite newbie here - I''m working through this like-hate relationship with Ruby and Rails right now... sometimes things work really well (like blobs seem to rock) but other times, I dunno! :-) Anyway, I''d like put in create and update user timestamps on all my primary domain tables and allow them to be updated automatically by ActiveRecord. Coming from Hibernate, I just

With after triggers in Postgres, there are special NEW and OLD vars accessible to trigger functions. Any such thing in Rails? Or would it entail doing something like setting a class var in before_update? Jack -- Posted via http://www.ruby-forum.com/.

Hello. LoginSystem is cool, it populates the @session instance variable of controllers with many useful info. The fact is : it would be cool to let models know about the session, too. For instance, after_update and after_create callbacks could store *who* did *what* on *what. Aim : having ActiveRecord::Base::session defined, returning the @session of the controller which manipulates the

I''m building a login system, and I want users to be able to update their password, first name and last name after signing up. So, when signing up password can''t be nil, and it must be between 6..20 characters long. However, on update, the user can choose to leave the password field empty (but fill in other stuff, like first name) and then I want the User model to not update

Hi all ! I''m having an issue and I can''t seem to make heads or tails of it. I am attempting to add an observer to a model object. I created app/models/greenback_transaction_observer.rb, inherited from AR::Observer, defined methods, registered in config/environment.rb, but things don''t work... So, I took a step back and put in the following code: class

has anyone has any idea how to implement audit trail table for all update / deletion done on records? I''m thinking to have corresponding audit trail table to each table, so everthing before an update or deletion is done, a new record will be insert into the corresponding audit trail table. Is there a way to overwrite the save, destroy, method at the application level? so that I do not

I''m looking for a way to generate some sort of logging/auditing of various events in my application, such as: - user logged in - user logged out - user clicked on a certain link - password attempt was wrong etc. For each, a numeric code along with some data (i.e. the username) would be great. Or even some sort of hash stored in the data field would be good. Another table could

Is there a built-in way to determine if a model object has just been created (ie. this object was the one that was originally persisted)? I can''t see it anywhere in the AR code, but thought I''d check. I want something like: p = Person.create p.original_instance? # true Is this built-in or should I just patch AR? -Jonathan.

I''ve installed the acts_as_versioned gem, and it shows up as installed when i do a "gem list" After installing it, I set up my new model with the "acts_as_versioned" line in its model file. I think went to run my migration to create this table, and I got the following error: == CreateDpslevels: migrating ================================================ --

Hey guys and gals, I have the following object that has acts_as_versioned: class Note < ActiveRecord::Base acts_as_versioned belongs_to :user end The schema for my notes table is as follows: create_table :notes, :force => true do |t| t.column :id, :integer t.column :noteshare_id, :integer t.column :user_id, :integer t.column :title, :string

Hi All, Rails newbie here trying to set up acts_as_versioned according to Chapter 14 in the Rails Recipies book. I''ve taken the following steps (nearly verbatim) as mentioned by the book: - created the target model "Post" - added the "acts_as_versioned" label to the model file - generated a migration file - added the table creation code and the command

Hi all, Despite switching to mod_fcgid (which has improved performance), sessions are still expiring sporadically. I thought I might try switching to storing them in the db, but I get the following error when I try to run the rake create_sessions_table command D:\User\Code\ruby\prometheus>rake create_sessions_table (in D:/User/Code/ruby/prometheus) rake aborted! undefined local variable or

Hi, I am trying to replace my old database trigger with ActiveRecord callbacks in rails. I have a model like following: class Action < ActiveRecord::Base belongs_to :inquiry def after_update #clean up all action associated with the inquiry. Action.update_all("latest = ''''", ["inquiry_id = ?", self.inquiry_id]) #find the latest action

Hi people I have tried to install the acts_as_versioned gem from github in rails 2.2.2 but it seems to conflict with some methods in the activerecords dirty.rb-file. I can solve some of the problem by changing code in the activerecord, but I don''t think that was the intention. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to

If I have several models which exhibit the same functionality, it seems makes sense to create a mixin, ''include'' it in each model and save myself some work and repeated code. Where can I define a module which will be available to all models? I can''t seem to find a documented place for them. Alternatively, is there a Rails-standard way of achieving the effect? Ben

Greetings! I''m attempting to use the act_as_versioned plugin to provide versioning functionality for my rails app, but can''t think my way through this: How can you use act_as_versioned to perform versioning on a HABTM join table? It is easy to see how to do so for join models (:has_many :through) but not so for the join table. I want to use act_as_versioned to maintain

I am looking at using acts_as_versioned to manage revisions of data in several tables in my application. However, the default behavior of acts_as_versioned appears to apply to individual rows within a table. The tables I want to version are complicated lookup tables and what I really want is to version the entire contents of each table as a single set. Adding a row, deleting a row, or updating