Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6857245
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T01:59:31+00:00 2026-05-27T01:59:31+00:00

If I define the following model… class Foo include DataMapper::Resource property :name, String, :key

  • 0

If I define the following model…

class Foo
  include DataMapper::Resource
  property :name, String, :key => true

  before :save,  do
    puts 'save'
  end
  before :update,  do
    puts 'update'
  end
end

Why does the 2nd save also trigger the ‘update’ hook?

ruby :001 > f = Foo.new
 => #<Foo @name=nil> 
ruby :002 > f.name = 'Bob'
 => "Bob" 
ruby :003 > f.save
save
 => true 
ruby :004 > f.name = 'Joe'
 => "Joe" 
ruby :005 > f.save
save
update
 => true 

Of course I could dive into the source and answer the question of what code drives this behavior. More importantly, I want to understand the right way to use each of these hooks in practice.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T01:59:32+00:00Added an answer on May 27, 2026 at 1:59 am
    require 'rubygems'
    require 'data_mapper'
    
    class Foo
      include DataMapper::Resource
    
      property :name, String, :key => true
    
      before :create,  do
        puts 'Create: Only happens when saving a new object.'
      end
    
      before :update,  do
        puts 'Update: Only happens when saving an existing object.'
      end
    
      before :save,  do
        puts 'Save: Happens when either creating or updating an object.'
      end
    
      before :destroy,  do
        puts 'Destroy: Only happens when destroying an existing object.'
      end
    end
    
    DataMapper.setup :default, 'sqlite::memory:'
    DataMapper.finalize
    DataMapper.auto_migrate!
    
    puts "New Foo:"
    f = Foo.new :name => "Fighter"
    f.save
    
    puts "\nUpdate Foo:"
    f.name = "Bar"
    f.save
    
    puts "\nUpdate Foo again:"
    f.update :name => "Baz"
    
    puts "\nDestroy Foo:"
    f.destroy
    

    Which returns:

    New Foo:
    Save: Happens when either creating or updating an object.
    Create: Only happens when saving a new object.
    
    Update Foo:
    Save: Happens when either creating or updating an object.
    Update: Only happens when saving an existing object.
    
    Update Foo again:
    Save: Happens when either creating or updating an object.
    Update: Only happens when saving an existing object.
    
    Destroy Foo:
    Destroy: Only happens when destroying an existing object.
    

    So as you can see you’d want to use :save hooks whenever something should happen after either a create or an update, and :create and/or :update when you want a finer level of control.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have following models relation: class Section(models.Model): section = models.CharField(max_length=200, unique=True) name = models.CharField(max_length=200,
I have a model similar to the following: class Foo attr_accessor :attribute_a # Really
Recently I saw the following code that creates a class in javascript: var Model.Foo
Consider the following models and form: class Pizza(models.Model): name = models.CharField(max_length=50) class Topping(models.Model): name
I have the following model: public class ExchangeRate { [Key, Column(Order = 1)] public
All, i have the following model defined, class header(models.Model): title = models.CharField(max_length = 255)
I wish to define the following typeclass Mapping : {-# LANGUAGE MultiParamTypeClasses #-} class
The following code works fine #define open { #define close } #include<stdio.h> #define int
I'm having a problem testing the following model: class Bill < ActiveRecord::Base belongs_to :consignee
I think I'm loosing my mind, why doens't the following work? class Parent(db.Model): childrenKeys

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.