Custom UUID generation in MariaDB conflicts with Ephemeral

[iamdriz]

In our Rails app (v7.2) we're manually generating the UUID's due to our use of Postgres and MariaDb (depending on environments, MariaDB doesn't support UUID generation, and we want to avoid having schemas and migrations that handle DB specific logic where possible). In our ApplicationRecord we have the following callback:

class ApplicationRecord < ActiveRecord::Base
  primary_abstract_class

  before_create :set_uuid

  private

  def set_uuid
    self.id ||= SecureRandom.uuid
  end
end

So this automatically sets the UUID for all of our models regardless of whether the DB does it out of the box.

And then we monkey-patch the Noticed ApplicationRecord under /lib/noticed/application_record.rb

module Noticed
  class ApplicationRecord < ::ApplicationRecord
    self.abstract_class = true
  end
end

This has allowed us to create Notifications and Events manually (to prove the monkey-patch works).

However it seems when calling deliver, we end up with an error:

Mysql2::Error: Field 'id' doesn't have a default value (ActiveRecord::NotNullViolation)

Line of code we're referencing that uses Ephemeral class (could this be the cause?):

noticed/app/models/concerns/noticed/deliverable.rb

Line 67 in 00b5f96

if self < Ephemeral

Our manual creation of UUID's works fine with other gems and our main application code, hence why it seems Ephemeral could be the cause. Any ideas for solutions? (other than dropping the manual UUID creation :D)

[iamdriz]

I've decided we'll just enforce Postgres going forward to avoid this issue.