diff options
Diffstat (limited to 'db')
-rw-r--r-- | db/migrate/20231216203855_create_events.rb | 10 | ||||
-rw-r--r-- | db/schema.rb | 21 | ||||
-rw-r--r-- | db/seeds.rb | 9 |
3 files changed, 40 insertions, 0 deletions
diff --git a/db/migrate/20231216203855_create_events.rb b/db/migrate/20231216203855_create_events.rb new file mode 100644 index 0000000..37cab03 --- /dev/null +++ b/db/migrate/20231216203855_create_events.rb @@ -0,0 +1,10 @@ +class CreateEvents < ActiveRecord::Migration[7.1] + def change + create_table :events do |t| + t.date :date + t.string :name + + t.timestamps + end + end +end diff --git a/db/schema.rb b/db/schema.rb new file mode 100644 index 0000000..fd03a50 --- /dev/null +++ b/db/schema.rb @@ -0,0 +1,21 @@ +# 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_12_16_203855) do + create_table "events", force: :cascade do |t| + t.date "date" + t.string "name" + t.datetime "created_at", null: false + t.datetime "updated_at", null: false + end + +end diff --git a/db/seeds.rb b/db/seeds.rb new file mode 100644 index 0000000..4fbd6ed --- /dev/null +++ b/db/seeds.rb @@ -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 |