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
Note: The legacy database I'm dealing with use multiple schemas. When I run rake db:schema:dump, it returns an inaccurate representation of the database, and rake db:structure:dump returns
defncopy: error: [host].[database_with_multiple_schemas].dbo.[specific_table] not found
rake aborted!
Note: dbo is the wrong schema but it uses it by default
Error dumping database
Thanks for the comments. I think this issue duplicates two others. The first #317 as that pertains to different schemas and the :ruby schema dumper format. I think this is where you want to focus your attention.
The second is ActiveRecord's alternative structure dump. Basically now we have defncopy which I am almost sure may not be any better for you. The latest 0.9.5.beta versions of TinyTDS when compiled against the latest 0.95 FreeTDS have bugs fixed in defncopy, but that tool only goes so far. Please follow issue #437 for that. I suspect it'll be a few months at least till we see that one come to fruition.
Note: The legacy database I'm dealing with use multiple schemas. When I run rake db:schema:dump, it returns an inaccurate representation of the database, and rake db:structure:dump returns
As per the doc (https://github.com/rails-sqlserver/AdventureWorks.Ruby#test-database-tasks) I added override_task.rb and databases.rake to fix defncopy oddities. However, after running rake db:structure: dump I get the following error:
The text was updated successfully, but these errors were encountered: