Change ActiveRecord::Migration to ActiveRecord::Migration[7.1] #788
Conversation
Changed the line ActiveRecord::Migration to ActiveRecord::Migration[7.1] so that schema loading could work (it is now required for newer versions of Rails) Updated and commented out the load schema task since it fails to find and run the loading of data into the database PostgreSQL container Added the initialize_profile method and add it to the `after_create` portion of the User factory because of the NameError I encountered: NameError: undefined local variable or method `init_profile' for #<FactoryBot::SyntaxRunner:0x00007eaac2e3c560> (NameError)
| def initialize_profile | ||
| create_profile!( | ||
| checkin_reminder: true, | ||
| onboarding_step_id: "onboarding-personal", | ||
| most_recent_doses: {}, | ||
| most_recent_conditions_positions: {}, | ||
| most_recent_symptoms_positions: {}, | ||
| most_recent_treatments_positions: {} | ||
| ) | ||
| end | ||
|
|
||
| factory :user do | ||
| sequence(:email) { |number| "user#{number}@example.com" } | ||
| password { "password123" } | ||
| password_confirmation { "password123" } | ||
| after(:create) { initialize_profile } |
There was a problem hiding this comment.
Modified the User factory to have the init_profile model from the User model and renamed it to initialize_profile because of the error below:
Done.
bin/rails aborted!
NameError: undefined local variable or method `init_profile' for #<FactoryBot::SyntaxRunner:0x00007eaac2e3c560> (NameError)
after(:create) { init_profile }
^^^^^^^^^^^^
Did you mean? initialize
/app/spec/factories/users.rb:45:in `block (3 levels) in <top (required)>'
/app/db/seeds/development/users.seeds.rb:4:in `block in evaluate'
/app/db/seeds/development/users.seeds.rb:3:in `each'
/app/db/seeds/development/users.seeds.rb:3:in `evaluate'
Tasks: TOP => db:seed => db:seed:development => db:seed:development:users
(See full trace by running task with --trace)
| end | ||
| Rake::Task["db:structure:load"].invoke | ||
| #Rake::Task["db:schema:load"].invoke |
There was a problem hiding this comment.
Had to comment out the db:schema:load task, after updating from db:structure:load since this was removed in Rails 6.2, in order to be able to run the rails app:setup command.
The error I got when I tried to run rails db:schema:load independently was:
psql:/app/db/structure.sql:60: ERROR: relation "ar_internal_metadata" already exists
bin/rails aborted!
failed to execute:
psql --set ON_ERROR_STOP=1 --quiet --no-psqlrc --output /dev/null --file /app/db/structure.sql flaredown_development
Please check the output above for any errors and make sure that `psql` is installed in your PATH and has proper permissions.
/app/lib/tasks/app.rake:47:in `build_database'
/app/lib/tasks/app.rake:32:in `setup'
/app/lib/tasks/app.rake:4:in `block (2 levels) in <top (required)>'
Tasks: TOP => db:schema:load
(See full trace by running task with --trace)It seems psql needs to be installed in the Rails container in order for the schema loading to work. Not sure why since pg is in the backend/Gemfile and I would think that should cover the database connection needs for the app.
There was a problem hiding this comment.
I'm curious if it would work as intended if we put the db:migrate here, and then the schema:load within the Rails.env.development? block. I'm not sure if this is ran in our deploy process for production anyway, or this is generally just used for development purposes.
There was a problem hiding this comment.
I wouldn't know since I was running this for development setup purposes 🙃
Maybe the contributors who've deployed Flaredown in production can comment?
| end | ||
| Rake::Task["db:structure:load"].invoke | ||
| #Rake::Task["db:schema:load"].invoke |
There was a problem hiding this comment.
I'm curious if it would work as intended if we put the db:migrate here, and then the schema:load within the Rails.env.development? block. I'm not sure if this is ran in our deploy process for production anyway, or this is generally just used for development purposes.
| def change | ||
| create_table :positions do |t| | ||
| t.string :postal_code, null: false | ||
| t.string :location_name, null: false | ||
| t.decimal :latitude, {precision: 10, scale: 7} | ||
| t.decimal :longitude, {precision: 10, scale: 7} | ||
| #t.decimal :longitude, {precision: 10, scale: 7} |
There was a problem hiding this comment.
Was this causing a problem?
There was a problem hiding this comment.
Probably the migration was failing to go through with the field as is. Can check and confirm.
after_createportion of the User factory because of the NameError I encountered: