Data not saving in 1.8.2 and upgrading from 1.8.2 to 1.9.0+discussion

Also, please let me know if any other information is required?

I'm a little confused about the 1.8 error. What mysql adapter are you using? If your database.yml file has "mysql" and not "mysql2" I would certainly change that. Hmmm, now that I think about it, that version still depended upon the userstamp plugin in vendor/plugins; that would have been the piece that set the value created_by. Is that plugin gone? There are no plugins used in 1.9.

As for the 1.9 migration error, I had not seen that before, but someone else (Pieter Vijfvinkel) actually mentioned it this morning. It's going to be a little tricky to debug this without access to a database where this is happening, but perhaps you'd be willing to add this debug statement to alter lines 138-140 of db/migrate/20120327090000_codename_table.rb to read as follows:

puts Rails.logger.info( ":read card = #{Card[:read].name}, :all card = #{Card[:all].name}, *all+*read = #{Card['*all+*read'].content}" )

puts Rails.logger.warn( "adding card for codename #{name}" )

card = if name=='*double_click'

... and then try running the migration again?

  --Ethan McCutchen.....2012-11-01 18:15:00 +0000

also, please let me know what os / ruby version you're using.

  --Ethan McCutchen.....2012-11-01 18:15:24 +0000

you could also try adding Wagn::Cache.reset_global in that same spot.

  --Ethan McCutchen.....2012-11-02 02:02:02 +0000

Please pull the latest code from github. Bugs were found and fixed in ruby 1.8.7.

  --Ethan McCutchen.....2012-11-08 17:39:59 +0000

Thanks for your help on this. I've been able to upgrade to wagn 1.9.1 now without running into any issues.

  --Ali ibrahim.....2012-11-14 03:01:22 +0000