search for: savepoints

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 and MySQL support savepoints (didn''t check others). I was thinking to make a custom patch for AR to create savepoints for inner transactions. Can somebody help me...

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

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

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

...uel was designed in a way that it won''t allow users to directly manipulate connections and control where to start and end transactions. So it only provides a block-based approach: Here is how this would be implemented in Sequel (assuming a decent database like PostgreSQL that supports savepoints - if that is not the case, just remove the :savepoint option): DB.transaction(savepoint: true, rollback: :always) do # sandboxed database access here: u = User[1] u.name = ''Changed'' u.save_changes end I have a similar issue with the design of RSpec lack of an around...

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

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

...ver. > This works using rsync's hard-link option to minimize wasted disk space. > This means that the recovery process is just copying the files you need. > Also, graceful recovery for downtime and optimistic disk space usage are > both very nice. (it will try to keep as many backup savepoints as it can > disk space depending) > > I'm evaluating ZFS and will likely include some features of ZFS into > BBuddy as we integrate these capabilities into our backup processes. > We're free to do this in part because we have redundant backup sets, so > a single failure wo...