ddollar/valkyrie

valkyrie's Issues

wrong number of arguments (0 for 1) (ArgumentError)

Currently throws the following stack trace:

    Transferring 16 tables:
    /var/lib/gems/1.8/gems/valkyrie-0.0.2/lib/valkyrie/progress_bar.rb:146:in `to_s': wrong number of arguments (0 for 1) (ArgumentError)
    from /var/lib/gems/1.8/gems/valkyrie-0.0.2/lib/valkyrie/progress_bar.rb:146:in `sprintf'
    from /var/lib/gems/1.8/gems/valkyrie-0.0.2/lib/valkyrie/progress_bar.rb:146:in `show'
    from /var/lib/gems/1.8/gems/valkyrie-0.0.2/lib/valkyrie/progress_bar.rb:32:in `initialize'
    from /var/lib/gems/1.8/gems/valkyrie-0.0.2/lib/valkyrie/cli.rb:23:in `new'
    from /var/lib/gems/1.8/gems/valkyrie-0.0.2/lib/valkyrie/cli.rb:23:in `start'
    from /var/lib/gems/1.8/gems/valkyrie-0.0.2/lib/valkyrie/database.rb:19:in `call'
    from /var/lib/gems/1.8/gems/valkyrie-0.0.2/lib/valkyrie/database.rb:19:in `transfer_to'
    from /var/lib/gems/1.8/gems/valkyrie-0.0.2/lib/valkyrie/database.rb:18:in `each'
    from /var/lib/gems/1.8/gems/valkyrie-0.0.2/lib/valkyrie/database.rb:18:in `transfer_to'
    from /var/lib/gems/1.8/gems/valkyrie-0.0.2/lib/valkyrie/cli.rb:20:in `start'
    from /var/lib/gems/1.8/gems/valkyrie-0.0.2/bin/valkyrie:7
    from /usr/local/bin/valkyrie:19:in `load'
    from /usr/local/bin/valkyrie:19

Sqlite -> Postgres / Model ID's

When transferring data from Sqlite to Postgres, the auto-incrementing 'trigger' for the model-id is lost.

In Sqlite, the ID field is stored as an integer. In Postgres, after running db:migrate, ID is a serial field. But after transferring data with Valkyrie, ID is changed to an integer field. Then when you try to add a record, you get a validation error because the ID value is not generated.

Using taps, data transfer from Sqlite to Postgres works OK.

Issue with Postgres schemas

Awesome gem, I've been using it for a bit and it is very simple and powerful. I do have 1 suggestion though. Recently, I have been working on a rails app that is using postgres schemas. When trying to use valkyrie, it would just dump all data from my remote server into my public schema. As an improvement, it would be awesome if there was an optional parameter to let you pass in the name of schemas :)