yamldb / yaml_db Goto Github PK

Is this project still being maintained? The last few issues have received no responses. There have been multiple attempts to add single table support that have fizzled with responses of "needs cleanup" but too general for the author to improve upon. What is the current state of the project?

Hello,
I use Mac OS X to develop and deploy on Linux. On my machine, there is no libyaml installed thus Ruby uses 'syck' as a yaml engine, but on Linux, it uses 'psyck' because libyaml is present.

yaml_db works perfectly with 'syck' but I noticed it fails with 'psyck' for me.

Dumping with yaml_db
psych:

- - 2
  - ! '40, Obama road , #04-03  Building'
  - Singapore
  - 234332
  - SG
  - !!null

syck:

  - - 2
    - "40, Obama road , #04-03  Building"
    - Singapore
    - 577185
    - SG
    -

Loading
yaml_db doesn't complain while dumping but those difference make yaml_db:load fail.

 You have a nil object when you didn't expect it!
 You might have expected an instance of Array.
 The error occurred while evaluating nil.each
 /usr/local/rvm/gems/ruby-1.9.2-p180/gems/yaml_db-0.2.1/lib/serialization_helper.rb:85:in `load_records'

it's easily reproducible (ruby 1.9.2 / rails 3.0.7):

rvm package install libyaml
rvm remove 1.9.2
rvm install 1.9.2
rails new my_app
cd my_app
rails g scaffold users name:string role:string
rake db:migrate
rake db:fixtures:load
rake db:dump 
rake db:load

`
Solution
Could force the parser to use syck: YAML::ENGINE.yamler= 'syck'
but if user has selected his parser, this might erase his setting. Is there a way to backup user parser to put it back in place? If there is an exception is it bad?

http://stackoverflow.com/questions/4980877/rails-error-couldnt-parse-yaml

It would be extremely helpful if there were a way to call rake db:data:dump that gave you the output via STDOUT instead of dumping the output to a file.

It appears that yaml_db doesn't dump empty tables, which means that it doesn't know to truncate them when loading. This was definitely unexpected. It is fairly easy to resolve, but before I create a pull request (including extending the test suite to validate the behavior), I'd like to know if there's a consensus that this behavior should be changed. In case anyone else wants my monkey-patch in the interim, here is my monkey patch for 0.2.3:

module SerializationHelper
  class Load
    def self.load_records(table, column_names, records)
      if column_names.nil?
        return
      end
      columns = column_names.map{|cn| ActiveRecord::Base.connection.columns(table).detect{|c| c.name == cn}}
      quoted_column_names = column_names.map { |column| ActiveRecord::Base.connection.quote_column_name(column) }.join(',')
      quoted_table_name = SerializationHelper::Utils.quote_table(table)
      (records || []).each do |record|
        quoted_values = record.zip(columns).map{|c| ActiveRecord::Base.connection.quote(c.first, c.last)}.join(',')
        ActiveRecord::Base.connection.execute("INSERT INTO #{quoted_table_name} (#{quoted_column_names}) VALUES (#{quoted_values})")
      end
    end
  end

  class Dump
    def self.dump_table(io, table)
      dump_table_columns(io, table)
      dump_table_records(io, table)
    end
  end
end

The modification to SerializationHelper::Load::load_records is to substitute an empty array for records if the latter is missing. The modification to SerializationHelper::Dump.dump_table is to eliminate the first line that returns if the table has no records.

Dear All:

I have a posts.yml, like this:

  ---
  posts:
    columns:
    - id
    - status
    - user_id
    - text
    records:
    - - 1
      - 1
      - 3
      - "Hi, every one."
    - - 2
      - 1
      - 3
      - "\u{9019}\u{4ef6}\u{6d0b}\u{88dd}\u{597d}\u{8b9a}\u{ff01}\u{8acb}\u{5927}\u{5bb6}\u{8a55}\u{5206}"

and I did a command to termial:

  rake db:data:load 

she told me

** Invoke db:data:load_dir (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:data:load_dir
rake aborted!
couldn't parse YAML at line 16 column 10
/Users/easter1021/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:148:in `parse'
/Users/easter1021/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:148:in `parse_stream'
/Users/easter1021/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:198:in `load_stream'
/Users/easter1021/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych/deprecated.rb:28:in `load_documents'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/yaml_db-0.2.2/lib/yaml_db.rb:60:in `load_documents'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/yaml_db-0.2.2/lib/serialization_helper.rb:57:in `block in load'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/activerecord-3.1.3/lib/active_record/connection_adapters/abstract/database_statements.rb:192:in `transaction'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/yaml_db-0.2.2/lib/serialization_helper.rb:56:in `load'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/yaml_db-0.2.2/lib/serialization_helper.rb:40:in `block in load_from_dir'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/yaml_db-0.2.2/lib/serialization_helper.rb:36:in `each'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/yaml_db-0.2.2/lib/serialization_helper.rb:36:in `load_from_dir'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/yaml_db-0.2.2/lib/tasks/yaml_db_tasks.rake:42:in `block (3 levels) in <top (required)>'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `call'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `block in execute'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `each'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `execute'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/task.rb:158:in `block in invoke_with_call_chain'
/Users/easter1021/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/task.rb:144:in `invoke'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/application.rb:116:in `invoke_task'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `block (2 levels) in top_level'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `each'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `block in top_level'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/application.rb:88:in `top_level'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/application.rb:66:in `block in run'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/lib/rake/application.rb:63:in `run'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2.2/bin/rake:33:in `<top (required)>'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/bin/rake:19:in `load'
/Users/easter1021/.rvm/gems/ruby-1.9.2-p290/bin/rake:19:in `<main>'
Tasks: TOP => db:data:load

I guess error what is encode problem.

how can I do to void this problem? thx all....

I'm getting the above error on a normal rake db:data:dump, our app is

Ruby 1.9.3-p125
Rails 3.0.9
Yaml_db 0.2.3

Switching back to yaml_db 0.2.2 worked fine. Here's the trace

** Invoke db:data:dump (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:data:dump
rake aborted!
TypeError: wrong argument type Arel::SelectManager (expected String): #Arel::SelectManager:0x00000005d5c370
/home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/activerecord-3.0.9/lib/active_record/connection_adapters/abstract_adapter.rb:207:in rescue in log' /home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/activerecord-3.0.9/lib/active_record/connection_adapters/abstract_adapter.rb:199:inlog'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/activerecord-3.0.9/lib/active_record/connection_adapters/postgresql_adapter.rb:514:in execute' /home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/activerecord-3.0.9/lib/active_record/connection_adapters/postgresql_adapter.rb:1004:inselect_raw'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/activerecord-3.0.9/lib/active_record/connection_adapters/postgresql_adapter.rb:997:in select' /home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/activerecord-3.0.9/lib/active_record/connection_adapters/abstract/database_statements.rb:7:inselect_all'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/activerecord-3.0.9/lib/active_record/connection_adapters/abstract/query_cache.rb:56:in select_all' /home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/yaml_db-0.2.3/lib/serialization_helper.rb:185:inblock in each_table_page'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/yaml_db-0.2.3/lib/serialization_helper.rb:183:in each' /home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/yaml_db-0.2.3/lib/serialization_helper.rb:183:ineach_table_page'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/yaml_db-0.2.3/lib/yaml_db.rb:46:in dump_table_records' /home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/yaml_db-0.2.3/lib/serialization_helper.rb:168:indump_table'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/yaml_db-0.2.3/lib/serialization_helper.rb:151:in block in dump' /home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/yaml_db-0.2.3/lib/serialization_helper.rb:149:ineach'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/yaml_db-0.2.3/lib/serialization_helper.rb:149:in dump' /home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/yaml_db-0.2.3/lib/serialization_helper.rb:14:indump'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125/gems/yaml_db-0.2.3/lib/tasks/yaml_db_tasks.rake:21:in block (3 levels) in <top (required)>' /home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/task.rb:205:incall'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/task.rb:205:in block in execute' /home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/task.rb:200:ineach'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/task.rb:200:in execute' /home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/task.rb:158:inblock in invoke_with_call_chain'
/home/swearwords/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/monitor.rb:211:in mon_synchronize' /home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/task.rb:151:ininvoke_with_call_chain'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/task.rb:144:in invoke' /home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/application.rb:116:ininvoke_task'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/application.rb:94:in block (2 levels) in top_level' /home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/application.rb:94:ineach'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/application.rb:94:in block in top_level' /home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/application.rb:133:instandard_exception_handling'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/application.rb:88:in top_level' /home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/application.rb:66:inblock in run'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/application.rb:133:in standard_exception_handling' /home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/lib/rake/application.rb:63:inrun'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/gems/rake-0.9.2.2/bin/rake:33:in <top (required)>' /home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/bin/rake:19:inload'
/home/swearwords/.rvm/gems/ruby-1.9.3-p125@global/bin/rake:19:in `

I ran into some issues with the behavior of SerializationHelper::Load.truncate_table when using yaml_db on a PostgreSQL database that had referential integrity. In order to assist in resolving the referential integrity issues, I needed to add CASCADE to the TRUNCATE statement. In order to get the rescue block to work within a transaction, I had to add SAVEPOINT and ROLLBACK statements. My monkey-patch only works for PostgreSQL, and may not work if you're not within a transaction, so getting this ready for inclusion into the actual code base would require adding database-specific support to yaml_db as well as transaction detection logic. I'd be happy to work on a pull request, but before I do I'd like to see some consensus on the desirability of resolving this issue and some discussion of approaches (should I embed the database-specific code in truncate_table or should I enable more generic support for database-specific code across the code base).

Here's my monkey-patch:

module SerializationHelper
  class Load
    def self.truncate_table(table)
      begin
        ActiveRecord::Base.connection.execute("SAVEPOINT before_truncation")
        ActiveRecord::Base.connection.execute("TRUNCATE #{SerializationHelper::Utils.quote_table(table)} CASCADE")
      rescue Exception
        ActiveRecord::Base.connection.execute("ROLLBACK TO SAVEPOINT before_truncation")
        ActiveRecord::Base.connection.execute("DELETE FROM #{SerializationHelper::Utils.quote_table(table)}")
      end
    end
  end
end

When using foreign key constraints (for example when using foreign_key_migrations or redhillonrails) in your database, 'rake db:load' may fail due to the fact that a load order is required when truncating or loading tables. This may result in errors like this (postgres):

PGError: ERROR: current transaction is aborted, commands ignored until end 
of transaction block 
: DELETE FROM schema_info 

I don't know if there's a way to temporarily disable foreign key migrations in postgres (maybe 'SET CONSTRAINTS ALL DEFERRED' could work), but nonetheless this issue might help others experiencing the same problem.

There is now a community-maintained fork at https://github.com/yamldb/yamldb. Please go there to contribute.

i'm using latest bundler, and i couldn't run the rake task. Perhaps you could make it work neatly with bundler.

Thanks

My environment have:
rails (3.0.9)
yaml_db (0.2.3)
Ruby 1.9.2-p290

This happen as soon as I run rake db:data:dump

rails 4, out of the box running either:

• bundle exec rake db:data:dump
• bundle exec rake db:data:dump_dir

Hello,

Could you please make it easier to use the rake tasks when using yaml_db as a Gem?

There's an easier way to allow rake tasks to be loaded when a library is used as a Gem instead of as a plug in. For thinking sphinx it's

require "thinking_sphinx/tasks"

in the Rakefile:

http://github.com/freelancing-god/thinking-sphinx/blob/master/lib/thinking_sphinx/tasks.rb

It is possible to run on heroku?

If I'm trying to load a dump with yaml_db, I see following message:

➜ rake db:data:dump && rake db:data:load --trace
** Invoke db:data:load (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:data:load
rake aborted!
/home/ytaras/projects/RLM/perforce/brpm/hotfix/2.6-D/Portal/db/data.yml: couldn't parse YAML at line 16 column 2
org/jruby/ext/psych/PsychParser.java:270:in `parse'
/home/ytaras/.rvm/rubies/jruby-1.6.8/lib/ruby/1.9/psych.rb:148:in `parse_stream'
/home/ytaras/.rvm/rubies/jruby-1.6.8/lib/ruby/1.9/psych.rb:198:in `load_stream'
/home/ytaras/.rvm/rubies/jruby-1.6.8/lib/ruby/1.9/psych/deprecated.rb:28:in `load_documents'
/home/ytaras/.rvm/gems/jruby-1.6.8/gems/yaml_db-0.2.3/lib/yaml_db.rb:60:in `load_documents'
/home/ytaras/.rvm/gems/jruby-1.6.8/gems/yaml_db-0.2.3/lib/serialization_helper.rb:57:in `load'
/home/ytaras/.rvm/gems/jruby-1.6.8/gems/activerecord-3.2.6/lib/active_record/connection_adapters/abstract/database_statements.rb:192:in `transaction'
/home/ytaras/.rvm/gems/jruby-1.6.8/gems/yaml_db-0.2.3/lib/serialization_helper.rb:56:in `load'
/home/ytaras/.rvm/gems/jruby-1.6.8/gems/yaml_db-0.2.3/lib/serialization_helper.rb:31:in `load'
/home/ytaras/.rvm/gems/jruby-1.6.8/gems/yaml_db-0.2.3/lib/tasks/yaml_db_tasks.rake:35:in `(root)'
org/jruby/RubyProc.java:258:in `call'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `execute'
org/jruby/RubyArray.java:1620:in `each'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `execute'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/task.rb:158:in `invoke_with_call_chain'
/home/ytaras/.rvm/rubies/jruby-1.6.8/lib/ruby/1.9/monitor.rb:201:in `mon_synchronize'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/task.rb:144:in `invoke'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/application.rb:116:in `invoke_task'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `top_level'
org/jruby/RubyArray.java:1620:in `each'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `top_level'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/application.rb:88:in `top_level'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/application.rb:66:in `run'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/lib/rake/application.rb:63:in `run'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/bin/rake:33:in `(root)'
org/jruby/RubyKernel.java:1097:in `load'
/home/ytaras/.rvm/gems/jruby-1.6.8@global/gems/rake-0.9.2.2/bin/rake:19:in `'
org/jruby/RubyKernel.java:1117:in `eval'
/home/ytaras/.rvm/gems/jruby-1.6.8/bin/ruby_noexec_wrapper:14:in `(root)'
Tasks: TOP => db:data:load
➜ ruby -v
jruby 1.6.8 (ruby-1.9.2-p312) (2012-09-18 1772b40) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_32) [linux-amd64-java]

Here's the beginning of a file:

➜ head db/data.yml -n 16

---
activity_attributes:
  columns:
  - id
  - name
  - required
  - input_type
  - attribute_values
  - created_at
  - updated_at
  - from_system
  - type
  - field
  - list_id
...

Looks like psych doesn't understand three dots (...) sequence - and I'm not able to switch to sych as it's not supported in JRuby 1.6.8, 1.9 source mode.

http://pastie.org/1024029

Hi,

I'm trying to use yaml_db but I get the error seen in that pastie. I followed the instructions in the README so I think it should work.

Matt

I'm getting this error using activerecord-sqlserver-adapter.

app> $ RAILS_ENV=production rake db:data:dump --trace
** Invoke db:data:dump (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:data:dump
rake aborted!
expected SCALAR, SEQUENCE-START, MAPPING-START, or ALIAS
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:24:in `scalar'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:24:in `visit_Psych_Nodes_Scalar'
/usr/lib/ruby/1.9.1/psych/visitors/visitor.rb:15:in `visit'
/usr/lib/ruby/1.9.1/psych/visitors/visitor.rb:5:in `accept'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:29:in `block in visit_Psych_Nodes_Sequence'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:29:in `each'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:29:in `visit_Psych_Nodes_Sequence'
/usr/lib/ruby/1.9.1/psych/visitors/visitor.rb:15:in `visit'
/usr/lib/ruby/1.9.1/psych/visitors/visitor.rb:5:in `accept'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:29:in `block in visit_Psych_Nodes_Sequence'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:29:in `each'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:29:in `visit_Psych_Nodes_Sequence'
/usr/lib/ruby/1.9.1/psych/visitors/visitor.rb:15:in `visit'
/usr/lib/ruby/1.9.1/psych/visitors/visitor.rb:5:in `accept'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:29:in `block in visit_Psych_Nodes_Sequence'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:29:in `each'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:29:in `visit_Psych_Nodes_Sequence'
/usr/lib/ruby/1.9.1/psych/visitors/visitor.rb:15:in `visit'
/usr/lib/ruby/1.9.1/psych/visitors/visitor.rb:5:in `accept'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:19:in `block in visit_Psych_Nodes_Document'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:19:in `each'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:19:in `visit_Psych_Nodes_Document'
/usr/lib/ruby/1.9.1/psych/visitors/visitor.rb:15:in `visit'
/usr/lib/ruby/1.9.1/psych/visitors/visitor.rb:5:in `accept'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:13:in `block in visit_Psych_Nodes_Stream'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:13:in `each'
/usr/lib/ruby/1.9.1/psych/visitors/emitter.rb:13:in `visit_Psych_Nodes_Stream'
/usr/lib/ruby/1.9.1/psych/visitors/visitor.rb:15:in `visit'
/usr/lib/ruby/1.9.1/psych/visitors/visitor.rb:5:in `accept'
/usr/lib/ruby/1.9.1/psych/nodes/node.rb:46:in `to_yaml'
/usr/lib/ruby/1.9.1/psych.rb:190:in `dump'
/usr/lib/ruby/1.9.1/psych/core_ext.rb:14:in `psych_to_yaml'
/var/lib/gems/1.9.1/gems/yaml_db-0.3.0/lib/yaml_db.rb:27:in `chunk_records'
/var/lib/gems/1.9.1/gems/yaml_db-0.3.0/lib/yaml_db.rb:49:in `block in dump_table_records'
/var/lib/gems/1.9.1/gems/yaml_db-0.3.0/lib/serialization_helper.rb:186:in `block in each_table_page'
/var/lib/gems/1.9.1/gems/yaml_db-0.3.0/lib/serialization_helper.rb:182:in `each'
/var/lib/gems/1.9.1/gems/yaml_db-0.3.0/lib/serialization_helper.rb:182:in `each_table_page'
/var/lib/gems/1.9.1/gems/yaml_db-0.3.0/lib/yaml_db.rb:47:in `dump_table_records'
/var/lib/gems/1.9.1/gems/yaml_db-0.3.0/lib/serialization_helper.rb:167:in `dump_table'
/var/lib/gems/1.9.1/gems/yaml_db-0.3.0/lib/serialization_helper.rb:150:in `block in dump'
/var/lib/gems/1.9.1/gems/yaml_db-0.3.0/lib/serialization_helper.rb:148:in `each'
/var/lib/gems/1.9.1/gems/yaml_db-0.3.0/lib/serialization_helper.rb:148:in `dump'
/var/lib/gems/1.9.1/gems/yaml_db-0.3.0/lib/serialization_helper.rb:14:in `dump'
/var/lib/gems/1.9.1/gems/yaml_db-0.3.0/lib/tasks/yaml_db_tasks.rake:21:in `block (3 levels) in '
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/task.rb:240:in `call'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/task.rb:240:in `block in execute'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/task.rb:235:in `each'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/task.rb:235:in `execute'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain'
/usr/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/task.rb:172:in `invoke_with_call_chain'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/task.rb:165:in `invoke'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:150:in `invoke_task'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:106:in `block (2 levels) in top_level'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:106:in `each'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:106:in `block in top_level'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:115:in `run_with_threads'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:100:in `top_level'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:78:in `block in run'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'
/var/lib/gems/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:75:in `run'
/var/lib/gems/1.9.1/gems/rake-10.4.2/bin/rake:33:in `'
/usr/local/bin/rake:19:in `load'
/usr/local/bin/rake:19:in `'
Tasks: TOP => db:data:dump

Some info about my environment :

# bundle show
Gems included by the bundle:
  * actionmailer (3.2.22)
  * actionpack (3.2.22)
  * activemodel (3.2.22)
  * activerecord (3.2.22)
  * activerecord-sqlserver-adapter (3.2.13)
  * activeresource (3.2.22)
  * activesupport (3.2.22)
  * arel (3.0.3)
  * builder (3.0.4)
  * bundler (1.3.5)
  * coderay (1.1.0)
  * erubis (2.7.0)
  * hike (1.2.3)
  * i18n (0.6.11)
  * journey (1.0.4)
  * jquery-rails (3.1.3)
  * json (1.8.3)
  * mail (2.5.4)
  * mime-types (1.25.1)
  * multi_json (1.11.2)
  * net-ldap (0.3.1)
  * polyglot (0.3.5)
  * rack (1.4.7)
  * rack-cache (1.2)
  * rack-openid (1.4.2)
  * rack-ssl (1.3.4)
  * rack-test (0.6.3)
  * rails (3.2.22)
  * railties (3.2.22)
  * rake (10.4.2)
  * rbpdf (1.18.6)
  * rdoc (3.12.2)
  * redcarpet (2.3.0)
  * request_store (1.0.5)
  * rmagick (2.13.4)
  * ruby-openid (2.3.0)
  * sprockets (2.2.3)
  * thor (0.19.1)
  * tilt (1.4.1)
  * tiny_tds (0.6.2)
  * treetop (1.4.15)
  * tzinfo (0.3.44)
  * yaml_db (0.3.0)

# ruby --version
ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]

the db:data:dump method appears to no longer work for postgres when using Rails 3.2. This method worked fine for me with Rails 3.1.3 but when I moved to RaIls 3.2 I received the error from line 184 in the serialization_helper.

I'm trying to convert from SQLite3 to MySQL.

As per the instructions in the readme, I ran rake db:dump and created a data.yml file which looked like it had everything in it.

I updated my database.yml to access MySQL and created the dev and test databases.

Running rake db:load successfully created the schema in the dev database, but I received an error when the script started trying to load in the data:

You have a nil object when you didn't expect it!
You might have expected an instance of Array.

Doing some debugging of the script revealed that data['records'] was not finding anything in the data.yml file. When I commented out the three hyphens --- after the word "records" for each table in the file, all the data was successfully loaded.

In other words, the following excerpt from my YAML file worked:

slugs:
columns:

• id
• name
• sluggable_id
• sequence
• sluggable_type
• scope
• created_at
• locale
  records:
  #---
• - 1
  • home
  • 1
  • 1
  • Page
  • !!null
  • '2011-04-25 23:33:22.554123'
  • en

Worked.

There was no binary data in my very small, non-customised refinery CMS database.

Trying to do a dump and this is what I am getting

C:\Development\rails\automation_metrics_tool>rake db:data:dump --trace
** Invoke db:data:dump (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:data:dump
rake aborted!
undefined method []=' for #<ActiveRecord::Result:0x47bb570> C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/serialization_helper.rb:10 8:inblock in unhash_records'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/activerecord-4.1.0.rc1/lib/active_record/res
ult.rb:55:in block in each' C:/Ruby200/lib/ruby/gems/2.0.0/gems/activerecord-4.1.0.rc1/lib/active_record/res ult.rb:55:ineach'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/activerecord-4.1.0.rc1/lib/active_record/res
ult.rb:55:in each' C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/serialization_helper.rb:10 7:ineach_with_index'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/serialization_helper.rb:10
7:in unhash_records' C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/yaml_db.rb:47:inblock in
dump_table_records'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/serialization_helper.rb:18
7:in block in each_table_page' C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/serialization_helper.rb:18 3:ineach'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/serialization_helper.rb:18
3:in each_table_page' C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/yaml_db.rb:46:indump_tab
le_records'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/serialization_helper.rb:16
8:in dump_table' C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/serialization_helper.rb:15 1:inblock in dump'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/serialization_helper.rb:14
9:in each' C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/serialization_helper.rb:14 9:indump'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/serialization_helper.rb:14
:in dump' C:/Ruby200/lib/ruby/gems/2.0.0/gems/yaml_db-0.2.3/lib/tasks/yaml_db_tasks.rake:2 1:inblock (3 levels) in <top (required)>'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/task.rb:236:in call' C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/task.rb:236:inblock i
n execute'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/task.rb:231:in each' C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/task.rb:231:inexecute
'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/task.rb:175:in block i n invoke_with_call_chain' C:/Ruby200/lib/ruby/2.0.0/monitor.rb:211:inmon_synchronize'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/task.rb:168:in invoke_ with_call_chain' C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/task.rb:161:ininvoke'

C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:149:in invoke_task' C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:106:in
block (2 levels) in top_level'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:106:in each' C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:106:in
block in top_level'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:115:in run_with_threads' C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:100:in
top_level'
C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:78:in b lock in run' C:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:165:in
standard_exception_handling'

I've downloaded the rails 2 branch into the plugin directory but the following error is shown:

 rake db:data:dump
(in /home/jfong/biorails/enterprise/trunk)
Configuring for Native RUBY
Compound Plugin: Biorails Demo Compound Inventory
rake aborted!
no such file to load -- rails/railtie
/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- rails/railtie (MissingSourceFile)
    from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `polyglot_original_require'
    from /home/jfong/biorails/enterprise/trunk/vendor/gems/polyglot-0.3.1/lib/polyglot.rb:64:in `require'
    from /home/jfong/biorails/enterprise/trunk/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `require'
    from /home/jfong/biorails/enterprise/trunk/vendor/rails/activesupport/lib/active_support/dependencies.rb:547:in `new_constants_in'
    from /home/../trunk/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `require'
    from /home/../trunk/vendor/plugins/yaml_db/lib/yaml_db.rb:6
    from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
    from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `polyglot_original_require'
    from /home/../trunk/vendor/gems/polyglot-0.3.1/lib/polyglot.rb:64:in `require'
    from /home/../trunk/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `require'
    from /home../trunk/vendor/rails/activesupport/lib/active_support/dependencies.rb:547:in `new_constants_in'
    from /home/../trunk/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `require'
    from /home/../trunk/vendor/plugins/yaml_db/init.rb:1:in `evaluate_init_rb'
    from /home../trunk/config/../vendor/rails/railties/lib/rails/plugin.rb:158:in `evaluate_init_rb'
    from /home../trunk/vendor/rails/activesupport/lib/active_support/core_ext/kernel/reporting.rb:11:in `silence_warnings'
    from /home././trunk/config/../vendor/rails/railties/lib/rails/plugin.rb:154:in `evaluate_init_rb'
    from /home../trunk/config/../vendor/rails/railties/lib/rails/plugin.rb:48:in `load'
    from /home/../trunk/config/../vendor/rails/railties/lib/rails/plugin/loader.rb:38:in `load_plugins'
    from /home/../trunk/config/../vendor/rails/railties/lib/rails/plugin/loader.rb:37:in `each'
    from /home/../trunk/config/../vendor/rails/railties/lib/rails/plugin/loader.rb:37:in `load_plugins'
    from /home/../trunk/config/../vendor/rails/railties/lib/initializer.rb:369:in `load_plugins'
    from /home/../trunk/config/../vendor/rails/railties/lib/initializer.rb:165:in `process'
    from /home/../trunk/config/../vendor/rails/railties/lib/initializer.rb:113:in `send'
    from /home/../trunk/config/../vendor/rails/railties/lib/initializer.rb:113:in `run'
    from /home/../trunk/config/environment.rb:27
    from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
    from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
    from /home/../vendor/rails/railties/lib/commands/about.rb:1
    from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
    from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
    from script/about:4

I'm using Rails 2.3.9

About your application's environment
Ruby version              1.8.7 (i486-linux)
RubyGems version          1.3.7
Rack version              1.1
Rails version             2.3.9
Active Record version     2.3.9
Active Resource version   2.3.9
Action Mailer version     2.3.9
Active Support version    2.3.9
Edge Rails revision       b492d494214a17f0050222ac724a65c8d0881805
Environment               development
Database adapter          mysql

I have also tried to use the master as a plugin as some of the commits mentioned that it can be used as a plugin in Rails 2, but both gave me the same error. Is it something obvious that I'm missing?

When I try to dump out my MySQL database, I get the following error:

NameError: undefined local variable or method `config' for main:Object
/Users/ykravchenko/Projects/appsec/config/application.rb:9:in `<top (required)>'
/Users/ykravchenko/Projects/appsec/Rakefile:4:in `require'
/Users/ykravchenko/Projects/appsec/Rakefile:4:in `<top (required)>'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/gems/rake-10.3.2/lib/rake/rake_module.rb:28:in `load'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/gems/rake-10.3.2/lib/rake/rake_module.rb:28:in `load_rakefile'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/gems/rake-10.3.2/lib/rake/application.rb:687:in `raw_load_rakefile'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/gems/rake-10.3.2/lib/rake/application.rb:94:in `block in load_rakefile'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/gems/rake-10.3.2/lib/rake/application.rb:176:in `standard_exception_handling'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/gems/rake-10.3.2/lib/rake/application.rb:93:in `load_rakefile'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/gems/rake-10.3.2/lib/rake/application.rb:77:in `block in run'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/gems/rake-10.3.2/lib/rake/application.rb:176:in `standard_exception_handling'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/gems/rake-10.3.2/lib/rake/application.rb:75:in `run'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/gems/rake-10.3.2/bin/rake:33:in `<top (required)>'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/bin/rake:23:in `load'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/bin/rake:23:in `<main>'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in `eval'
/Users/ykravchenko/.rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in `<main>'

Hey

I am trying to migrate for n postgres database to mysql.
When I run rake db:dump everything works.
When I run rake db:load it gives me an nil.each error.
I know I have empty tables, can you advise what I need to do.

Thanks

I run:

rake db:data:dump with:
ruby 1.9.3
rails ('3.2.3)
yaml_db (0.2.2)
sqlite3 (1.3.6) .

I get:

undefined method `add_limit_offset!' for #ActiveRecord::ConnectionAdapters::SQLite3Adapter:0xb5b4a40

home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/yaml_db-0.2.2/lib/serialization_helper.rb:184:in block in each_table_page' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/yaml_db-0.2.2/lib/serialization_helper.rb:183:ineach'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/yaml_db-0.2.2/lib/serialization_helper.rb:183:in each_table_page' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/yaml_db-0.2.2/lib/yaml_db.rb:46:indump_table_records'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/yaml_db-0.2.2/lib/serialization_helper.rb:168:in dump_table' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/yaml_db-0.2.2/lib/serialization_helper.rb:151:inblock in dump'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/yaml_db-0.2.2/lib/serialization_helper.rb:149:in each' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/yaml_db-0.2.2/lib/serialization_helper.rb:149:indump'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/yaml_db-0.2.2/lib/serialization_helper.rb:14:in dump' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/yaml_db-0.2.2/lib/tasks/yaml_db_tasks.rake:21:inblock (3 levels) in <top (required)>'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/task.rb:205:in call' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/task.rb:205:inblock in execute'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/task.rb:200:in each' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/task.rb:200:inexecute'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/task.rb:158:in block in invoke_with_call_chain' /home/matias/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/monitor.rb:211:inmon_synchronize'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/task.rb:151:in invoke_with_call_chain' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/task.rb:144:ininvoke'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/application.rb:116:in invoke_task' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/application.rb:94:inblock (2 levels) in top_level'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/application.rb:94:in each' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/application.rb:94:inblock in top_level'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/application.rb:133:in standard_exception_handling' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/application.rb:88:intop_level'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/application.rb:66:in block in run' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/application.rb:133:instandard_exception_handling'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/lib/rake/application.rb:63:in run' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/gems/rake-0.9.2.2/bin/rake:33:in<top (required)>'
/home/matias/.rvm/gems/ruby-1.9.3-p0@wow/bin/rake:19:in load' /home/matias/.rvm/gems/ruby-1.9.3-p0@wow/bin/rake:19:in

I tried using yaml_db to migrate data from sqlite to mysql, after performing:

1. rake db:dump

2. edit config/database.yml - change adapter to mysql2

3. rake db:load

every character that was a multibyte utf8 character in the original database got turned into question mark symbols(????)

The user of most advanced fork could create a new gem, this way it will keep the user merits, like what happened with gem cancan (ryanb/cancan#994) and this way we can continue contributing.

@onesup I've used onesup/yaml_db with Rails 4.0.5 with success:

gem 'yaml_db', git: 'git://github.com/onesup/yaml_db.git'

Thanks.

Hi,

This looks great but I would like to be able to select only specific tables to be dumped, rather than all of them.

Thanks

The inclusion of the time produces invalid directory names due to the colons.

Changing line 27 of yaml_db_tasks.rake to:

dir = ENV['dir'] || "#{Time.now.to_s.gsub(/ /, '_').gsub(/\:/,"-")}"

fixes the problem, replacing colons with dashes.

Rails 2.3.8 gives this:

DEPRECATION WARNING: Rake tasks in vendor/plugins/yaml_db/tasks are deprecated. Use lib/tasks instead. (called from <top (required)> at ***/gems/rails-2.3.8/lib/tasks/rails.rb:10)

Also, are we rails 3 compatible yet?

Same goes for rake db:load and rake db:data:load

As a new user, its unclear if these are exactly the same or if there is some difference between them that I'm not aware of.

Examples:
https://github.com/ludicast/yaml_db/blame/master/README.markdown#L21
https://github.com/ludicast/yaml_db/blame/master/README.markdown#L35

Is there a way to push a dump to heroku?

There is a related issue at jashmenn/activeuuid#70 - but as of yet I haven't received any advice on that on that end.

ActiveUUID provides a binary(16) field for databases that don't natively support UUIDs. In my case, MySQL. I'm trying to port to PostgreSQL, which does have support for UUIDs.

When a record looks like this:

#<TagWork id: #<UUID:0x3256dd8 UUID:00110954-44a5-4ce2-b067-3cf26a9ea631>, tag_id: #<UUID:0x3256824 UUID:a8bcfc8b-a94a-4236-97d2-dd18c9911fbd>, work_id: #<UUID:0x3256270 UUID:67e9a1d5-b225-4fef-8ea6-26e6dafccc59>, created_at: "2015-06-01 04:03:09", updated_at: "2015-06-01 04:03:09", deleted_at: nil>

MySQL exports like this:

tag_works:
columns:

• id
• tag_id
• work_id
• created_at
• updated_at
• deleted_at
  records:
• • !binary |-
    ABEJVESlTOKwZzzyap6mMQ==
  • !binary |-
    qLz8i6lKQjaX0t0YyZEfvQ==
  • !binary |-
    Z+mh1bIlT++Opibm2vzMWQ==
  • 2015-06-01 04:03:09.000000000 Z
  • 2015-06-01 04:03:09.000000000 Z
  • false

While PostgreSQL, in my tests, exports using the '00110954-44a5-4ce2-b067-3cf26a9ea631' format.

I've tried patching ActiveUUID, but nothing I've done seems to effect the export - I've assumed I needed to implement UUIDTools::UUID.to_yaml ... or dump, or somthing.

Any suggestions as to what need to be implemented to change the export format?

Problem has been found during migration from sqlite to postgres. Fix available in forked project (only one file affected)

http://github.com/xiwera/yaml_db

It would be great if you can add a way to limit a database dump or load to a single table by adding a table parameter to the rake task.

Ex.
rake db:data:dump["table_name"] -> Dump contents of Rails database table "table_name" to db/data.yml
rake db:data:load["table_name"] -> Load contents of db/data.yml into the database table "table_name"

I'm having issues comparing dump files generated by yaml_db because the tables don't dump in a consistent order. Records within a table dump in a consistent order because they are sorted by the first column, but the tables themselves can be returned in a random order from some database adapters. I resolved this with a simple monkey-patch, but before I work up a pull request I'd like to see if there's a consensus that resolving this is desirable.

Here's my monkey-patch (all it does is add a sort to the end of the chain):

module SerializationHelper
  class Dump
    def self.tables
      ActiveRecord::Base.connection.tables.reject { |table| ['schema_info', 'schema_migrations'].include?(table) }.sort
    end
  end
end

Anyone else having an issue where dump files are incomplete? I'm calling the gem directly from my rails app rather than using a rake task. I am calling it exactly as the rake task does. I ended up adding a flush and close after the dump and this solved my problem: AlbertGrimley@e5c3f34

The namespace is cluttered by SerializationHelper, etc.

The activerecord-sqlserver-adapter is not implementing the method.

This is the error:

This has been moved to the SQLServerCompiler in Arel.
/Users/tommasop/.rvm/gems/ruby-1.9.2-p290/gems/activerecord-sqlserver-adapter-3.1.1/lib/active_record/connection_adapters/sqlserver/database_statements.rb:72:in `add_limit_offset!'

When I run rake db:dump, I get the error:
rake aborted! ActiveRecord::ConnectionNotEstablished Tasks: TOP => db:dump => db:schema:dump

However, when I run rake db:data:dump I run into no problem.
Any ideas what's happening here?

Would be nice to know the progress of the dump/load.

I keep getting this error every time I try to run rake:db:data:dump. Any one else has had this error before?

Under which license is this software?

At some point recently, t.datetime schema objects in our production MySQL DB started dumping out as:

!ruby/object:Mysql::Time {}

I've poked at it a bit, but I can't figure out which of the recently upgraded components is causing the issue. We're using the following relevant gems:

Gems included by the bundle:

• actionmailer (3.1.3)
• actionpack (3.1.3)
• activemodel (3.1.3)
• activerecord (3.1.3)
• activeresource (3.1.3)
• activesupport (3.1.3)
• arel (2.2.1)
• aws (2.5.6)
• builder (3.0.0)
• bundler (1.0.18)
• capistrano (2.9.0)
• erubis (2.7.0)
• highline (1.6.8)
• hike (1.2.1)
• hpricot (0.8.5)
• http_connection (1.4.1)
• i18n (0.6.0)
• jquery-rails (1.0.19)
• json (1.6.2)
• mail (2.3.0)
• mime-types (1.17.2)
• multi_json (1.0.4)
• mysql (2.8.1)
• net-ldap (0.2.2)
• net-scp (1.0.4)
• net-sftp (2.0.5)
• net-ssh (2.2.1)
• net-ssh-gateway (1.1.0)
• polyglot (0.3.3)
• rack (1.3.5)
• rack-cache (1.1)
• rack-mount (0.8.3)
• rack-ssl (1.3.2)
• rack-test (0.6.1)
• rails (3.1.3)
• railties (3.1.3)
• rake (0.9.2.2)
• rdoc (3.11)
• route53 (0.2.1)
• ruby-hmac (0.4.0)
• sprockets (2.0.3)
• sqlite3 (1.3.4)
• thor (0.14.6)
• tilt (1.3.3)
• treetop (1.4.10)
• tzinfo (0.3.31)
• uuidtools (2.1.2)
• will_paginate (3.0.2)
• xml-simple (1.1.1)
• yaml_db (0.2.2)

I've done some searching, but haven't found anybody else reporting a similar problem, so hopefully we're just doing something dumb that's easy to fix.

Thanks!

Rails 3.1 and 3.2 both have i18n ~> 0.6 in their dependency trees, but i18n 0.7.0 (released 2014-12-19) requires Ruby 1.9.3.

Rails 3.1/3.2 users on Ruby <1.9.3 will have to pin i18n to 0.6 anyway, so this won't be a yaml_db-specific issue for them. However, it breaks CI builds.

(Meta-issue) Now that yaml_db has returned from a 2.5-year hiatus, does anyone think it should still support Rails 2.x? Please share your opinion.