Truncate the `security_findings` table

b0c86614 · Mehmet Emin INAC · pbair · 544adf54 · b0c86614 · b0c86614
Commit b0c86614 authored Dec 07, 2020 by Mehmet Emin INAC Committed by pbair Dec 10, 2020
Showing with 8 additions and 0 deletions

db/post_migrate/20201207151651_truncate_security_findings_table_2.rb ...rate/20201207151651_truncate_security_findings_table_2.rb +7 -0

db/schema_migrations/20201207151651 db/schema_migrations/20201207151651 +1 -0

No files found.
--- a/db/post_migrate/20201207151651_truncate_security_findings_table_2.rb
+++ b/db/post_migrate/20201207151651_truncate_security_findings_table_2.rb
+# frozen_string_literal: true
+
+require_relative Rails.root.join('db', 'post_migrate', '20201102152945_truncate_security_findings_table.rb')
+
+# This is the second time we are truncating this table
+# so the migration class name has choosen like this for this reason.
+class TruncateSecurityFindingsTable2 < TruncateSecurityFindingsTable; end
--- a/db/schema_migrations/20201207151651
+++ b/db/schema_migrations/20201207151651
+93def9138efddc9cd0ace5524dc5cf6cdc0221977083324c5c0ad3cf3fb75e55
\ No newline at end of file