Closed Imitat closed 1 year ago
Apologies, I resolved this and it's an issue local to me. Please feel free to delete this and thanks for the interesting code!
I resolved this and it's an issue local to me
Do you know what -- I had been trying to recreate what you describe with Sqlite and Postgres, and just no luck, and then ... when I tried with a fresh MySQL then it did fail in the same way that you describe!
So I will pursue a fix for those who have a fresh MySQL install :)
Thanks very much for reaching out -- inadvertently it's set the universe just that little bit more into alignment.
Hi, regret I didn't mention I'm using MySQL! I am, and was about to update that I do still see the issue. Thanks for your time and again, the interesting gem.
Okay -- to fix it for the moment, run mysql -uroot
and then this:
CREATE DATABASE automodels_development;
CREATE DATABASE automodels_test;
QUIT
And at that point you should be able to create migrations / do everything else normally.
As well in database.yml
if you wanted to point things to an existing MySQL database then that should work out pretty well, no more need to bin/rails db:...
anything.
Will let you know when this fix is available -- will also bundle in the Trix editor for larger :text fields. So a couple things coming along at once for the upcoming v1.0.118.
Excellent, thank you!
Okay, v1.0.118 has now shipped, which includes a fix for the bug that you had found. You can update your project by running:
bundle update brick
Thanks!
Hi, mentioning that in a brand new Rails 7 application (
gem "rails", "~> 7.0.4", ">= 7.0.4.2"
) w/gem 'brick'
in theGemfile
, I'm seeing the below when runningrake db:create
(orrails db:create
). Commenting Brick and re-running doesn't produce the error. Best!