You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While setting up cod-app for cloud, I realized that rails dbconsole would fail with unknown command-line client for #{database_name}.
I dug through the dbconsole source and attached a few puts to the dbconsole in cluster and observed the following output:
The regex match on the case predicate in dbconsole.rb will always fail since when /^(jdbc)?mysql/ begins with pedant, not mysql.
Not sure if this is worthy of a fix since I don't know how often rails dbconsole gets used, but a simple solution seems to be simply renaming the adapter to mysql_pedant.
While setting up
cod-app
for cloud, I realized thatrails dbconsole
would fail withunknown command-line client for #{database_name}
.I dug through the dbconsole source and attached a few
![screen shot 2018-01-17 at 12 37 20 pm](https://user-images.githubusercontent.com/31742287/35057533-40c0b630-fb83-11e7-9370-dc0b26313423.png)
puts
to the dbconsole in cluster and observed the following output:The regex match on the case predicate in
dbconsole.rb
will always fail sincewhen /^(jdbc)?mysql/
begins withpedant
, notmysql
.Not sure if this is worthy of a fix since I don't know how often
rails dbconsole
gets used, but a simple solution seems to be simply renaming the adapter tomysql_pedant
.cc @casperisfine, @goldenson
The text was updated successfully, but these errors were encountered: