Support for migrations_paths

[hlascelles]

We are using Rails' feature migrations_paths.

However activerecord-clean-db-structure errors with:

Errno::ENOENT: No such file or directory @ rb_sysopen - db/secondary_structure.sql (Errno::ENOENT)
..../gems/activerecord-clean-db-structure-0.4.3/lib/activerecord-clean-db-structure/tasks/clean_db_structure.rake:28:in `read'
..../gems/activerecord-clean-db-structure-0.4.3/lib/activerecord-clean-db-structure/tasks/clean_db_structure.rake:28:in `block (2 levels) in <main>'
..../gems/activerecord-clean-db-structure-0.4.3/lib/activerecord-clean-db-structure/tasks/clean_db_structure.rake:26:in `each'
..../gems/activerecord-clean-db-structure-0.4.3/lib/activerecord-clean-db-structure/tasks/clean_db_structure.rake:26:in `block in <main>'
..../gems/rake-13.2.1/lib/rake/task.rb:281:in `block in execute'

The structure is actually found at: db_other/secondary_structure.sql if the config is:

  secondary:
    adapter: ...
    migrations_paths:
      - "db_other/migrate"

Would you accept a PR to handle migrations_paths?

[lfittl]

Would you accept a PR to handle migrations_paths?

Sure, I think that makes sense to support. Appreciate the report & your effort to fix it.

[andyatkinson]

Agree w/ @lfittl this makes sense to support. I'm working on an application that uses migration_paths so I can help verify the changes.

[andyatkinson]

@hlascelles Did you get a chance to work on this?

[hlascelles]

No, apologies, we never did. We have a number of multi-column primary keys, and when we saw that was a limitation we had to abort, sorry.