Ingredients and MariaDB don't work well together

[mamhoff]

Steps to reproduce

Try using any Alchemy::Ingredient with a MariaDB database. You'll get an error such as:

$ rails alchemy:upgrade:6.0:create_ingredients 
Create ingredients for elements with ingredients defined
--------------------------------------------------------
-- Creating ingredients for 16 new_entry(s)
.rails aborted!
NoMethodError: undefined method `accessor' for #<ActiveRecord::Type::Text:0x00005590d6ea3140>
/home/anselm/.gem/ruby/2.6.9/gems/activerecord-6.0.4.4/lib/active_record/store.rb:217:in `store_accessor_for'
/home/anselm/.gem/ruby/2.6.9/gems/activerecord-6.0.4.4/lib/active_record/store.rb:212:in `write_store_attribute'
/home/anselm/.gem/ruby/2.6.9/gems/activerecord-6.0.4.4/lib/active_record/store.rb:136:in `block (3 levels) in store_accessor'
/home/anselm/.gem/ruby/2.6.9/gems/alchemy_cms-6.0.0/app/models/alchemy/ingredients/richtext.rb:37:in `strip_content'
/home/anselm/.gem/ruby/2.6.9/gems/activesupport-6.0.4.4/lib/active_support/callbacks.rb:428:in `block in make_lambda'

Expected behavior

The upgrader should create ingredients.

Reasons

MariaDB differs from MySQL in that they do not provide a native JSON datatype, and thus Rails does not know that the data column is, in fact, a JSON column. You can fix it by modifying the Alchemy::Ingredient class as such:

# /app/models/alchemy/ingredient_decorator
module Alchemy
  module IngredientDecorator
    def self.prepended(klass)
      klass.store :data, coder: JSON
    end
    Alchemy::Ingredient.prepend self
  end
end

We can't do this globally, because for MySQL and Postgres this is not necessary and will generate a bunch of warnings.
It is also hard to do conditionally, because we do not want to access the database on app startup.

System configuration

• Alchemy Version: 6.0.0
• Rails Version: 6.0.4.4