search for: active_record_1

Hi, I''m trying to upgrade an app from 2.2.2 to 2.3.2 and I get a bunch of Mysql Errors : Mysql::Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''RELEASE SAVEPOINT active_record_1'' at line 1: RELEASE SAVEPOINT active_record_1 Mysql version is 4.1.22 which supports save points but not the RELEASE SAVEPOINT command. I did a test under mysql console. So, - is Rails 2.3.2 incompatible with mysql 4.1.22 ? - is there a special Mysql adapter ? Thanks -- Posted via http...

...all should be okay" do file = File.new("test/files/lib/upload_sample.xml") upload = XmlUpload.create(:xml_contents => contents = file.read) ..... ..... end The create line is throwing up the following error ActiveRecord::StatementInvalid: Mysql2::Error: SAVEPOINT active_record_1 does not exist: ROLLBACK TO SAVEPOINT active_record_1 /Users/conor/.rvm/gems/ruby-1.9.2-p136/gems/activerecord-3.0.3/lib/ active_record/connection_adapters/abstract_adapter.rb:202:in `rescue in log'' /Users/conor/.rvm/gems/ruby-1.9.2-p136/gems/activerecord-3.0.3/lib/ active_record/c...

hello can anybody help me with this bug, (this sometimes occur sometimes passes) 1) ActiveRecord::StatementInvalid in ''MailReader on Simple Tasks should not accept duplicate email'' Mysql::Error: MySQL server has gone away: ROLLBACK TO SAVEPOINT active_record_1 /home/poldz/.gem/ruby/1.8/gems/activerecord-2.3.5/lib/active_record/connection_adapters/abstract_adapter.rb:219:in `log'' /home/poldz/.gem/ruby/1.8/gems/activerecord-2.3.5/lib/active_record/connection_adapters/mysql_adapter.rb:323:in `execute'' /home/poldz/.gem/ruby/1.8/gems/activer...

Rails 2.3.5 I am working on a nested form that assigns roles to users through a table called clearances. I have attr_acessable turned off globally in an initializer: ActiveRecord::Base.send(:attr_accessible, nil) I have this set in clearance.rb attr_accessible(:description, :effective_from, :role_id, :superceded_after, :user_id) And this is what params looks like after the

...When trying to use the same connection among the parent process and its children, I get into a total mess (due to concurrent access to the db connection). Sample errors from different runs: The famous "MySQL has gone away" Some other times it work perfectly! "Mysql::Error: SAVEPOINT active_record_1 does not exist" "undefined method all_hashes for nil:NilClass" I know that I have so many issues to handle here: concurrency safety, blocking DB adapter, the nature of the testing environment..etc But, is there another approach to handle it? What is the best practice of testing co...