Old project, migrations starting from first migration

[maxrails]

Hi, I'm using Rails 3.2.13 and application is rather old and huge. I installed octopus gem in gemfile:(gem 'ar-octopus', :git => 'https://github.com/tchandy/octopus.git') - set up schards.yml

octopus:
  fully_replicated: false
  verify_connection: true
  environments:
    - development
    - test
  development:
    slave1:
      adapter: mysql2
      encoding: utf8
      reconnect: false
      database: ns_dev_replica
      pool: 10
      username: root
      socket: /tmp/mysql.sock
      host: 127.0.0.1
  test:
    slave1:
      adapter: mysql2
      encoding: utf8
      reconnect: false
      database: ns_dev_replica_test
      pool: 10
      username: root
      socket: /tmp/mysql.sock
      host: 127.0.0.1

then bundle exec rake octopus:copy_schema_versions It start working correctly for select queries( tested in console ) but then I tried bundle exec rake db:migrate - and it started migrations from the beginning of my migrations. - and of course it breaks as master and slave already got all fields and tables. Is there way to pass schema version to octopus - so migrations will start not from the beginning ?

[yukihariguchi]

I also encountered this problem.

[england]

+1

[nsi88]

+1

[ashish198907]

+1

[knightq]

Same problem here, any news?