2.0.1 to 2.0.3 issues
Replies (4)
RE: 2.0.1 to 2.0.3 issues
-
Added by Tom Bodet over 12 years ago
Going back over my steps, I've come to realize I should have been doing the db:migrate first. So I'm actually stuck at the migrate step.
database.yml for development:
development:
adapter: mysql2
database: redmine
host: 192.168.111.22
username: redmine
password: <password no quotes around it>
encoding: utf8
rake db:migrate RAILS_ENV=development --trace
and get:
- Invoke db:migrate (first_time)
- Invoke environment (first_time)
- Execute environment
- Invoke db:load_config (first_time)
- Invoke rails_env (first_time)
- Execute rails_env
- Execute db:load_config
- Execute db:migrate
rake aborted!
undefined method `accept' for nil:NilClass
/usr/local/rvm/gems/ruby-1.9.3-p194/gems/activerecord-3.2.6/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in `to_sql'
<snip>
RE: 2.0.1 to 2.0.3 issues
-
Added by Tom Bodet over 12 years ago
Got this figured out.
When we didn't have the mysql2 entry in the database.yml the passenger error talked about the activerecord-mysql-adapter we thought adding the mysql2 version would help. Well that turned out to be the problem once we fixed the database config. Removing that gem got it up and running.
RE: 2.0.1 to 2.0.3 issues
-
Added by shreyas kr over 12 years ago
Hi,
I am also facing the same issues.
Can you explain more clearly how to fix the issue.
I have the following entry in database.yml
development:
adapter: mysql2
encoding: utf8
database: blog_development
pool: 5
username: root
password:
socket: /tmp/mysql.sock
RE: 2.0.1 to 2.0.3 issues
-
Added by LEXO IT Services Switzerland over 12 years ago
Exactly the same issue here. We're trying to upgrade Redmine 2.0.3 to 2.1 and switching from mysql to mysql2 adapter since it's recommended in the upgrade manual.
Our database.yml config:
production: adapter: mysql2 database: redmine host: localhost username: ### password: ### encoding: utf8
our configuration(s):
# bundle show Gems included by the bundle: * actionmailer (3.2.8) * actionpack (3.2.8) * activemodel (3.2.8) * activerecord (3.2.8) * activerecord-mysql2-adapter (0.0.3) * activeresource (3.2.8) * activesupport (3.2.8) * arel (3.0.2) * builder (3.0.0) * bundler (1.2.1) * coderay (1.0.7) * erubis (2.7.0) * fastercsv (1.5.5) * hike (1.2.1) * i18n (0.6.1) * journey (1.0.4) * jquery-rails (2.0.3) * json (1.7.5) * mail (2.4.4) * mime-types (1.19) * multi_json (1.3.6) * mysql (2.8.1) * mysql2 (0.3.11) * net-ldap (0.3.1) * pg (0.14.1) * polyglot (0.3.3) * rack (1.4.1) * rack-cache (1.2) * rack-openid (1.3.1) * rack-ssl (1.3.2) * rack-test (0.6.1) * rails (3.2.8) * railties (3.2.8) * rake (0.9.2.2) * rdoc (3.12) * rmagick (2.13.1) * ruby-openid (2.1.8) * sprockets (2.1.3) * sqlite3 (1.3.6) * thor (0.16.0) * tilt (1.3.3) * treetop (1.4.10) * tzinfo (0.3.33)
We're using debian squeeze with rubygems 1.8 and ruby 1.9.2.
I really hope someone can figure this out. We'll continue trying and post our results here if we find out something.
Additional note:
the 2.0.3 system runs fine with ruby 1.8 and the mysql database adapter.
update 23.09.2012 - SOLVED (for me)
I've just found out that it works well when using the old "mysql" adapter in the database.yml configuration. This is weird because this is the first try I'm doing with the update and using the mysql adapter with 2.1 has never worked before. But now it did. I guess I did something wrong with the ruby update in the previous updates that did not succeed. Anyway I think it should work with the mysql2 adapter as well since it's recommended by the upgrade manual. Well at least it works for now... not really a solution though but maybe this helps somebody else.