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 592857
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T15:47:02+00:00 2026-05-13T15:47:02+00:00

Given this example: class Server < ActiveRecord::Base has_many :clients,:dependent => :destroy after_destroy: delete_server_directory end

  • 0

Given this example:

class Server < ActiveRecord::Base
  has_many :clients,:dependent => :destroy 
  after_destroy: delete_server_directory
end

class Client < ActiveRecord::Base
  belongs_to :server

  before_destroy :copy_some_important_stuff_from_the_server_directory_before_its_too_late
end

Will this be the order of destruction when I call server.destroy?

  1. Server#clients, along with Client‘s before/after_destroy callbacks
  2. Server will be destroyed
  3. followed by the Server‘s after_destroy callback
  • 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-13T15:47:02+00:00Added an answer on May 13, 2026 at 3:47 pm

    You can very easily test. I took your code, and implemented the callbacks with a simple call to puts. Then launched script/console and had ActiveRecord log to the console:

    >> ActiveRecord::Base.logger = Logger.new(STDOUT)
    => #<Logger:0x0000000308d2f0 ...>
    

    Set up some basic environment:

    >> a = Client.create :name => 'Client 1'
      Client Create (0.4ms)   INSERT INTO "clients" ("name", "server_id") VALUES('Client 1', NULL)
    => #<Client id: 1, name: "Client 1", server_id: nil>
    >> b = Client.create :name => 'Client 2'
      Client Create (0.5ms)   INSERT INTO "clients" ("name", "server_id") VALUES('Client 2', NULL)
    => #<Client id: 2, name: "Client 2", server_id: nil>
    >> server = Server.create :name => 'The Server'
      Server Create (0.3ms)   INSERT INTO "servers" ("name") VALUES('The Server')
    => #<Server id: 1, name: "The Server">
    >> server.clients = [a, b]
      Client Load (0.4ms)   SELECT * FROM "clients" WHERE ("clients".server_id = 1) 
      Client Update (0.4ms)   UPDATE "clients" SET "server_id" = 1 WHERE "id" = 1
      Client Update (0.2ms)   UPDATE "clients" SET "server_id" = 1 WHERE "id" = 2
    => [#<Client id: 1, name: "Client 1", server_id: 1>, #<Client id: 2, name: "Client 2", server_id: 1>]
    

    And here’s the gist of it:

    >> server.destroy
    >>> copy_some_important_stuff_from_the_server_directory_before_its_too_late called!
      Client Destroy (0.5ms)   DELETE FROM "clients" WHERE "id" = 1
    >>> copy_some_important_stuff_from_the_server_directory_before_its_too_late called!
      Client Destroy (0.2ms)   DELETE FROM "clients" WHERE "id" = 2
      Server Destroy (0.2ms)   DELETE FROM "servers" WHERE "id" = 1
    >>> delete_server_directory called!
    => #<Server id: 1, name: "The Server">
    

    So it looks like you were dead on target. 🙂

    P.S.

    • There’s a small syntax error in the server model’s after_destroy.
    • I assume with step 1 you really meant before_destroy, as seen in your example.
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 368k
  • Answers 368k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer The Entity Framework designer is terrible - I've had the… May 14, 2026 at 5:11 pm
  • Editorial Team
    Editorial Team added an answer If by "hijack" you meant sniff the packets then what… May 14, 2026 at 5:11 pm
  • Editorial Team
    Editorial Team added an answer If you want two actions to be atomic, embed them… May 14, 2026 at 5:11 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

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.