similar to: rspec bug, on Mysql::Error: MySQL server has gone away: ROLLBACK TO SAVEPOINT active_record_1

Hi, I''m switching the database of a rails 3 app I have developed from postgres to mysql so that I can avail of amazon''s rds. Before I make the change I have been running my test code using mysql on my dev machine with the mysql2 adaptor . My test code is throwing up some errors that I haven''t quite been able to get to the bottom of yet. Basically I have a model that is

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

Hello! I experienced problems with testing transactions which are supposed to be rolled back, but are not, because of transactional fixtures eliminating the inner transaction. Can this be worked around somehow without turning off transactional fixtures? Maybe savepoints can help this? Does anyone have any experience with savepoints to achieve nested transaction functionality? Both Postgres

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

Hi, I implemented the IMAP example at the bottom of: http://wiki.rubyonrails.com/rails/pages/HowToReceiveEmailsWithActionMailer The receiver app (inbox.rb) works fine when I run it against my mail server with the following line commented out: MailReader.receive(to, body) But when I uncomment that line I get error: inbox.rb:15 uninitialized constant MailReader (NameError) There is of course

Hi All, I had a bug in one project, that data get duplicated in the DB due to multiple instances of the application (multiple thins) are accessing the DB at the same time .. The typical mistake. Problem fixed. I just need to write a test code that covers the fixed bug. I need to simulate the concurrent requests that can result in the original bug. I thought of many ideas and decided to go with

Recently I''ve found out some mentions to the "--sandbox" parameter to the "rails console" command. And I found the idea interesting, but since I''m using Sequel instead of ActiveRecord I guessed this wouldn''t work for me. But after talking about this subject in the Sequel mailing list, Jeremy Evans has brought to my attention that there are some

Hello, I''m having trouble with transactions with rails 3.0.3 and mysql 5. I''d like to import data etl-batch-style: class Job < ActiveRecord::Base # ... def perform_etl connection.transaction do extract # some connection.execute / job.update_attribute stuff transform # some connection.execute / job.update_attribute stuff end end #... end

My specs work fine with this in my Gemfile.lock: grep rspec Gemfile.lock rspec (2.11.0) rspec-core (~> 2.11.0) rspec-expectations (~> 2.11.0) rspec-mocks (~> 2.11.0) rspec-core (2.11.0) rspec-expectations (2.11.1) rspec-mocks (2.11.1) rspec-rails (2.11.0) rspec (~> 2.11.0) rspec-rails (~> 2.11) After "bundle update

Hi, I''m absolutely new to centralized server management, sorry sorry in advance for any stupid remarks. Looking on the puppet documentation, I mainly find a lot of info about how to manage the config files, but nothing about centralized control. So I''m wandering if I''m looking a the right software package for my needs. I want to be able to do the following from a

On 12/19/2013, 04:00 , lists at benjamindsmith.com wrote: > BackupPC is a great product, and if I knew of it and/or it was available > when I started, I would likely have used it instead of cutting code. Now > that we've got BackupBuddy working and integrated, we aren't going to be > switching as it has worked wonderfully for a decade with very few issues > and little