Feature #6852

Rake log task to log ActiveRecord changes

Added by Martin Ducar over 3 years ago. Updated over 3 years ago.

Status:Closed
Priority:Normal
Assigned To:Martin Ducar
Category:DB migrations
Target version:Sprint 27
Difficulty:trivial Bugzilla link:
Found in release: Pull request:https://github.com/theforeman/foreman/pull/1633
Story points-
Velocity based estimate-
Release1.6.0Release relationshipAuto

Description

When testing idempotency of seed files in automated way, we have found out that best solution would be to have db:seed run twice second time with log of ActiveRecord sql commands. That way we can filter is second run tries to do another updates, inserts, deletes,.... This might be use-full also for debugging purposes.

Associated revisions

Revision e09d72ee
Added by Martin Ducar over 3 years ago

fixes #6852 - `rake log` added to log ActiveRecord changes to stdout

History

#1 Updated by Dominic Cleal over 3 years ago

Note that there's a test in core for idempotency of db:seed which uses an expectation on #save, so this should flag up the problem with a full stack trace when run (test/lib/tasks/seeds_test.rb).

#3 Updated by Martin Ducar over 3 years ago

Ok, thanks for the hint than i think this feature is irrelevant

#4 Updated by Dominic Cleal over 3 years ago

Nah, after seeing the PR, I think that'll still be useful for all sorts, I'm happy to keep it.

#5 Updated by Dominic Cleal over 3 years ago

  • Status changed from New to Ready For Testing
  • Target version set to Sprint 27
  • Release set to 1.6.0
  • Pull request https://github.com/theforeman/foreman/pull/1633 added

#6 Updated by Martin Ducar over 3 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF