4 files changed, 45 insertions, 4 deletions

@@ -1,6 +1,6 @@
-class CreateWittlePuzzles < ActiveRecord::Migration[7.1]
+class CreatePuzzles < ActiveRecord::Migration[7.1]
   def change
-    create_table :wittle_puzzles do |t|
+    create_table :puzzles do |t|
       t.text :data
       t.text :solved_data
       t.string :category
@@ -1,6 +1,6 @@
-class CreateWittleScores < ActiveRecord::Migration[7.1]
+class CreateScores < ActiveRecord::Migration[7.1]
   def change
-    create_table :wittle_scores do |t|
+    create_table :scores do |t|
       t.references :puzzle, null: false
       t.string :name
       t.string :ip
@@ -0,0 +1,32 @@
+# This file is auto-generated from the current state of the database. Instead
+# of editing this file, please use the migrations feature of Active Record to
+# incrementally modify your database, and then regenerate this schema definition.
+#
+# This file is the source Rails uses to define your schema when running `bin/rails
+# db:schema:load`. When creating a new database, `bin/rails db:schema:load` tends to
+# be faster and is potentially less error prone than running all of your
+# migrations from scratch. Old migrations may fail to apply correctly if those
+# migrations use external dependencies or application code.
+#
+# It's strongly recommended that you check this file into your version control system.
+
+ActiveRecord::Schema[7.1].define(version: 2023_11_30_173513) do
+  create_table "puzzles", force: :cascade do |t|
+    t.text "data"
+    t.text "solved_data"
+    t.string "category"
+    t.datetime "created_at", null: false
+    t.datetime "updated_at", null: false
+  end
+
+  create_table "scores", force: :cascade do |t|
+    t.integer "puzzle_id", null: false
+    t.string "name"
+    t.string "ip"
+    t.integer "seconds_taken"
+    t.datetime "created_at", null: false
+    t.datetime "updated_at", null: false
+    t.index ["puzzle_id"], name: "index_scores_on_puzzle_id"
+  end
+
+end
@@ -0,0 +1,9 @@
+# This file should ensure the existence of records required to run the application in every environment (production,
+# development, test). The code here should be idempotent so that it can be executed at any point in every environment.
+# The data can then be loaded with the bin/rails db:seed command (or created alongside the database with db:setup).
+#
+# Example:
+#
+#   ["Action", "Comedy", "Drama", "Horror"].each do |genre_name|
+#     MovieGenre.find_or_create_by!(name: genre_name)
+#   end