similar to: SQL transaction rollback isn't logged !

Displaying 20 results from an estimated 100000 matches similar to: "SQL transaction rollback isn't logged !"

2011 May 08
1
Transaction - but no rollback?
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
2010 Jul 23
7
fail rollback transaction with manual raise exception
With : PostgreSQL 8.4 or postgresql-8.3 rails 2.3.4 pg 9.x or pg 8.x I test this code: ========================= class NkiBatch < ActiveRecord::Base Bank.connection.transaction do bank = Bank.new(:name => "ddsjdsjdsjk") bank.save! raise ActiveRecord::Rollback.new end end and this: ========================= class NkiBatch < ActiveRecord::Base
2006 Oct 20
2
how do you manually cause a rollback in a transaction?
how do you manually cause a rollback in a transaction? I''ve looked everywhere with no suceess. Anyone know? Thanks in advance Chris -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to
2007 Apr 08
8
SQLite3 build is broken because calling rollback!() doesn't prevent COMMIT
I know why SQLite3 is broken. This code: Topic.transaction do |transaction| transaction.rollback! end results in the following database commands: BEGIN; ROLLBACK; COMMIT; In other words, there is a COMMIT when no transaction is in flight. MySQL and Postgres are coll with it, but SQLite3 blows up with indignation. Recorded as a ticket: http://dev.rubyonrails.org/ticket/8030
2006 Oct 03
2
Rails transactions issue with rollback.
Hi, I have a transaction in which a duplicate key exception is being thrown by MySQL. I assume this happens when I try to do a save. The problem is that before the save, I do a destroy on another object as part of the transaction. Catching the exception by doing this, User.transaction do begin objA.destroy objB.save <-- causing exception rescue Exception => exc
2010 Dec 08
2
Bug in nested transactions in rails 2.3.x
Hello! According to ActiveRecord transactions documentation, User.transaction do User.create(:username => ''Kotori'') User.transaction(:requires_new => true) do User.create(:username => ''Nemu'') raise ActiveRecord::Rollback end end User.find(:all) # => Returns only Kotori But I get both records in database (tested on
2006 Oct 21
3
Transactions
Ok, how does everyone else do transactions in development mode? If I get a exception within a transaction, I get the ruby exception screen, I want rails to complete the block code, and then rollback the transaction. Is there a way to disable the exception screen before the transaction, and then enable it after the transaction? Thanks! --~--~---------~--~----~------------~-------~--~----~ You
2007 Apr 04
1
pontential bug in rspec_on_rails and ActiveRecord transactions
Hello rspec-users, I''ve encountered a strange bug in rspec, but it may be me who is wrong. I''m running latest version from the trunk (r1678) of both rspec and rspec_on_rails. Please consider the following model: class Url < ActiveRecord::Base def after_save Contact.create!(:primary_email => ''user at example.com'') raise
2008 Apr 30
6
best practice for object transaction?
I have a new @offer that needs to generate a document if saved. But that''s all or nothing: transaction do @offer.save! generate_document end # handle exceptions if needed If save! fails everything is fine, but if generate_document raises an exception @offer is left as a model with timestamps, id, which is not a new_record? anymore (though the database was
2007 Jun 02
2
Unit tests breaks with sqlite
Hi, I''m using an sqlite3 database with Rails and have some trouble running unit tests What I''ve done is * rails my_app * edited database.yml to use sqlite3 adapter, db/my_app_development and db/my_app_test * ruby script\generate model user * edited model class User < ActiveRecord::Base validates_presence_of :name validates_uniqueness_of :name end *
2005 Dec 22
13
in-memory SQLite for testing
I am following the rails book, and arrived to the section about testing. The test database is configured as: test: adapter: sqlite3 database: ":memory:" and I get this error with the simple product test: % ruby test/unit/product_test.rb Loaded suite test/unit/product_test Started E/usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/ errors.rb:94:in
2010 Mar 22
0
rspec bug, on Mysql::Error: MySQL server has gone away: ROLLBACK TO SAVEPOINT active_record_1
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
2005 Dec 23
2
SQLite in-memory
I left ":memory:" in database.yml for testing and the most simple tests in the Agile book do not work (see trace below for test_truth). Since that''s what comes with the distributed database.yml I suppose it''s me doing something wrong. Did someone get SQLite ":memory:" working? How does it grab the schema? -- fxn % rake test_units (in
2007 Nov 21
0
Testing transactional updates in story runner
How do you guys test transactional updates with story runner? I have an action that needs to update four different models: Enrollment.transaction do @contact.update_addresses(params[:contact_address], params [:billing_address]) @enrollment.update_attributes!(params[:enrollment]) end The last update_attributes! will raise ActiveRecord::RecordNotValid if anything was
2006 Jan 03
4
in-memory test database -- where''s the schema?
I''m trying to get the unit testing for a new project to use the wonderful :memory: database specification for SQLite. However, like many people before me, I can''t get the schema to import or have anything else useful. Initially, the error I get is: /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/errors.rb:94:in `check'': cannot rollback - no transaction is
2007 Jan 19
0
Do transactions fail with polymorphic has_one relationships?
I have an AR::Base descendant with a complex object graph beneath it, like so: ArtisanQuoteInput has_one QuoteInput and then QuoteInput has several objects attached to it. Note that the relationship between ArtisanQuoteInput and QuoteInput is polymorphic, so the relationship in A is written has_one :quote_input, :as => :program_quote_input If @artisan_quote_input is an instance of
2008 Aug 26
1
transaction not working with update_attributes!
I am trying to wrap the updating of two models in a transaction and when the transaction fails it is not rolling back. My method is : def update_attributes(user,params) @user = user @company = user.company begin User.transaction do @user.update_attributes!(params[:user]) @company.update_attributes!(params[:company]) end true rescue false
2007 Mar 29
1
How to restart server programmatically?
I need to be able to restart my server based on a specific database change. I''ve been trying a call to system("script/process/reaper -a graceful -d dispatch.fcgi") but that raises a transaction error which rolls back the save. I wasn''t aware that after_save would rollback. That''s potentially useful but pretty much not right now. Here''s my code: def
2007 Oct 08
3
test not rolling back
For testing, I use: self.use_transactional_fixtures = true This should cause a ROLLBACK for each test case. If I run a single file, foo_controller_test.rb, it works as expected. I see BEGIN and ROLLBACK 8 times in the log files. But if I run: rake test:functionals I get 3 COMMITs, 196 BEGINS and 193 ROLLBACKs. The code in fixtures.rb that deals with this is : def
2007 Dec 11
3
Transactional/Rollback problems
I''m having a rollback problem with rspec trunk. It doesn''t seem like rollbacks are happening quite as often as they should be. It appears as though the rollbacks are *NOT* occurring on the first description block in a file, but are for the rest. Here is a set of specs that are failing: require File.dirname(__FILE__) + "/../spec_helper" describe