[BUG?] Cannot create Noticed::Event in MariaDB #412
Unanswered
janpeterka
asked this question in
Q&A
Replies: 2 comments
-
MariaDB JSON columns are actually text columns with JSON constraints, so they don't work interchangeably with MySQL. I don't have any plans to support MariaDB but if someone wants to make a PR we can. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I ran into this issue with MariaDB too and was able to work around it by modifying the migration to use type longtext for params and overriding the Event class to include this line: serialize :params, JSON Not tested significantly, but so far it appears to be working. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Bug Report
Maybe this is wrong place to report this - I'm not sure if there's something wrong in this gem, or it's problem with ActiveSupport or some misconfiguration on my side.
Will be glad for help with that though, and if it seems like this is not
noticed
-related, I will understand if this will be just closed.Describe the Bug:
Running tests locally, I have no problem. Running them on my Gitlab runner, I'm getting error:
Digging deeper, I found out the difference is that my local tests are running on MySQL 8.0, and on runner I'm using MariaDB 10.11.6, which behave differently, using LONGTEXT and
json_valid
constaint.I then tried to get more info from console:
I guess it has trouble with having
=>
instead of:
in the saved hash.Why do we get that? Coder (or used
ActiveJob::Argument
, to be precise) does it, if I understand that code correctly.But! When I run the same code in local environment, I'm getting correct json:
So I'm really just confused on what's happening here 😅
Will be extremely grateful for any guidance!
Environment:
Checklist:
Beta Was this translation helpful? Give feedback.
All reactions