Closed tgeselle closed 7 years ago
This is really a Rails issue - take a look at the configure_connection
method in the Active Record abstract mysql adapter:
https://github.com/rails/rails/blob/master/activerecord/lib/active_record/connection_adapters/abstract_mysql_adapter.rb#L808
MemSQL certainly claims the ability to work with Rails, and suggests mysql2 as the preferred adapter: https://docs.memsql.com/v5.7/docs/how-to-connect-to-memsql#section-ruby-on-rails
I think you may get this working by adding sql_mode: ''
in your database.yml. I have a hunch that an empty value will resolve the issue.
@sodabrew Thanks for your help. It works by adding this to the database.yml file:
variables:
sql_mode: ''
Here's an example of my database.yml (it might helps people who have the same issue as me):
default: &default
adapter: mysql2
pool: 5
username: root
password:
host: 127.0.0.1
socket: '/memsql-ops/installs/master-3306/memsql.sock'
variables:
sql_mode: ''
I'm trying to configure a new Rails 5.0.2 project with MemSQL 5.7.4. I'm using the gem mysql in version 0.4.5. I also use a small model called Report that I created manually in my MemSQL's DB.
I have this issue with every request I try to send to MemSQL: