Closed ron-shinall closed 1 year ago
https://github.com/github/trilogy/pull/22 might fix this. I'll try to get a trilogy release out soon, but in the meantime you can try using:
gem "trilogy", git: "https://github.com/github/trilogy", ref: "main", glob: "contrib/ruby/trilogy.gemspec"
(And please do report back whether that works if you try it.)
Yep, that fixed the issue. All of our tests pass when using the repo main branch! Any ETA on a release? Thanks so much!
Version 2.1.2 released!
I ran into this issue when trying to switch our Rails 7.1 application to Trilogy, but I have the same issue if I generate a new rails app and try to use Trilogy. The application is using MariaDB.
Steps to reproduce
Generate a new Rails Edge app using MySQL:
Add the Trilogy gems to the Gemfile:
Install the gems:
Set the adapter to trilogy in
database.yml
:Attempt to create the database:
Expected behavior
Actual behavior
Full trace:
System configuration
Rails version: 7.1.0.alpha
Ruby version: ruby-3.1.2 [ arm64 ]
MariaDB version: 10.8.3-MariaDB Homebrew