similar to: "cannot start a transaction within a transaction" sqlite error on OS X Tiger but not Windows

Hi, by switching to MySQL from SQLite, it fixed the problem. I ran rdebug on it and it is trying to call I ActiveRecord::Base.connection.begin_db_transaction. from ActiveRecordSafetyListener.scenario_started. I don''t think SQLLite likes transactions. Ed On Nov 15, 2007 10:56 AM, Ed Howland <ed.howland at gmail.com> wrote: > If I run the story stand-alone, I get: > ruby

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

Hi, There seems to be an issue with SQLite adapter. Any idea what is causing it? document_test.rb contains default scaffold and works fine with MySQL but fails with SQLite. Other unit tests work fine with either DB. Sergei Serdyuk Red Leaf Software LLC http://www.redleafsoft.com document_test.rb: require File.dirname(__FILE__) + ''/../test_helper'' class DocumentTest <

I have an app that seems to run fine when I develop on windows, but in my linux deployment environment I get this error: uninitialized constant SQLite Here is the stack trace: /usr/lib/ruby/gems/1.8/gems/activesupport-1.0.4/lib/active_support/dependencies.rb:183:in `const_missing''

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 *

So after successfully getting the test SQLite db to run from memory, I tried running some tests but found that somewhere in the schema translation from Postgres (my devel database) and SQLite Rails fails to properly set the ''id'' column, which breaks all kinds of things. Take as an example my ''users'' table. In Postgres the schema is (generated with pgAdmin III):

Hello guys, I''m developing a new app in Rails, and every now and then I get an ActiveRecord error, I cannot reproduce exactly what triggers it, hope you can help me, or give me tips on debugging this kind of stuff. This time I got the error reporting page, but normally I would just see the 500.html page, with no info about what went wrong. This is the error (it''s the complete

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

I''m just starting my first rails app and I can''t figure out this error. It''s got something to do with connecting to sqlite3...Here''s the application trace: <code> /usr/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_support/dependencies.rb:200:in `const_missing''

I''m now using the 0.8.0 RC1 gem and have the same version of rspec and rspec_on_rails checked out into my vendor/plugins directory. I''m having a problems with controllers... I''ve generated a controller using the ./script/generate rspec_controller MyController. When I try to run the rake spec:controller task I get the following: euclid% rake spec:controllers (in

Greetings: I am using Sqlite3 database with my Rails app. When I try and run "rake tests" for the app it always fails with the error: ** Invoke default (first_time) ** Invoke test (first_time) ** Execute test ** Invoke test:units (first_time) ** Invoke db:test:prepare (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:test:prepare ** Invoke

Hello all. I am using BackgrounDRB with "great happiness and joy", however, I am running into one problem in that when I am running my tests with autotest using Sqlite3 3.3.17 I am getting "ActiveRecord::StatementInvalid" exception inside of the sqlite_adapter.rb:360 which is checking for an empty structure. I thought it might be the version of Sqlite, so I upgraded to 3.3.17

I am currently experiencing concurrency issues after moving from MySQL to SQLite. My original program worked fined using MySQL but is now returning "SQLite3::BusyException" errors. The same result happens whether or not I enable the allow_concurrency flag. If I do manually acquire a lock on the SQLite DB the problem would disapear, but I thought that rails was supposed to handle this

i'm building dovecot 1.1.beta9 on both osx 10.4.11 osx 10.5.1 using Using built-in specs. Target: powerpc-apple-darwin8 Configured with: /Builds/apple/gcc_42-5531/obj/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/usr/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-gxx-include-dir=/usr/include/c++/4.0.0

I am getting the following error using sqlite3. If I ran the same query directly in sqlite3 client, the data is saved without error. Same is happening for every table during inserts. SQLite3::SQLException: sessions.id may not be NULL: INSERT INTO sessions ("updated_at", "session_id", "data") VALUES(''2009-09-30 02:28:45'',

Hi, This is just kindof a RoR question, but since you all potentially do the same things as I do, I thought I''ll ask here.. Im trying to use the boolean type in the database. Migrations is no problem, it even converts the 0/1 values from my import CSV to false and true. However, I cannot make the :conditions part of a find work: Loading development environment (Rails 2.0.2) >> c

Any idea what would cause this? >> icps = Icp.find(:all) ActiveRecord::StatementInvalid: SQLite3::SQLException: unsupported file format: SELECT * FROM icps from c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_recor d/connection_adapters/abstract_adapter.rb:120:in `log'' from c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_recor

The build failed. CHANGES ------- Revision 8896 committed by bitsweat on 2008-02-19 02:56:05 Don''t assume all records from nested include are of same class. Closes #11154 [acechase] M /trunk/activerecord/lib/active_record/association_preload.rb A /trunk/activerecord/test/cases/associations/eager_load_nested_include_test.rb TEST FAILURES AND ERRORS ----------------------- Name:

hello it seems like this question has appeared a few times with no answer: how do you get rails to issue ''write'' statements (ie ''CREATE/UPDATE'') to the database without committing each time? I tried setting ActiveRecord::Base.connection.begin_db_transaction before calling any action on my object, but as soon as myObject.save or myObject.update is called,

Hi, I''ve been following this thread and I can get the example stories to run with the ruby command. But I''ve been unable to get the example from http://blog.davidchelimsky.net/articles/2007/10/25/plain-text-stories-part-iii to run with all.rb ruby stories/all.rb /home/edh/story/stories/additions/steps/addition_steps.rb:2: undefined method `steps_for'' for main:Object