similar to: Odd issue with SQLite & Rails.

I was prototyping a gui using a SQLite-backed Rails (on Windows). I wrote a seperate Ruby script to populate an events table with filler data. As part of some discussion I got it into my head to just fill up the table and see what kind of performance issues, metrics or database size issues I would be exposed to. The script was executed from the command line (i.e. 2 different processes) The script

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 <

Hello, When I kick off SVN1992 with storeconfigs=yes, I get the following error: err: Could not store configs: SQLite3::SQLException: SQL logic error or missing database: INSERT INTO resources ("exported", "line", "title", "host_id", "restype", "source_file_id") VALUES(NULL, 23, ''svnpkgadd-emacs-nox-etc'', NULL, NULL,

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, 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

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 *

Hello, I''m having some trouble getting stored configs to work properly with SQLite. During each run, the puppet master is reporting the following error: err: Could not store configs: SQLite3::SQLException: fact_values.value may not be NULL: INSERT INTO fact_values ("updated_at",3 18:41:56'', NULL, 3, 18) I''m using Puppet 0.24.4 with Rails 1.2.6 and SQLite

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

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

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

Hello, I recently updated Rails to 3.0.5. The very same code that worked on 3.0.3 now gives error. The code is: def kategorialista Kategoria.where(:elfogadva => TRUE).order("nev").collect {|s| [s.nev, s.sefuri]} end It is in application_controller.rb with helper_method :kategorialista The error it gives on 3.0.5: SQLite3::SQLException: no such table: kategoria: SELECT

CentOS Errata and Security Advisory 2015:1634 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1634.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 2764e452be02a51c8b3d271be95f244637de6d9bb673f767854cffe7bac683bb lemon-3.6.20-1.el6_7.2.i686.rpm

Bear with me, this is CentOS related. :) I have a python CGI that's behaving weirldy on Whitebox systems that've been switched over to CentOS 4 (ages ago, no other problems to speak of aside from this one). I've broken the problem down to a minimal test case... 1. Create a small database # sqlite3 /tmp/testcase.db 'CREATE TABLE testtable ( date date primary key unique, name

I''ve been editing a rails app on Windows for a little while now. I just checked it into source control and started editing on my iMac. Everything seems to run normally, except that when I attempt to modify the database in any way (I''m running sqlite), I get a weird error: "cannot start a transaction within a transaction"

Dear list, i have installed SQLiteDF (and SQlite 3.5.3 too) After the suggested dataframe generation iris.sdf <- sqlite.data.frame(iris) i have close R and than restart it for verify the correct load of dataframe : the file data1 is saved in the usual folder .SQLiteDF after the command : attachSdf("c:/R/Report/.SQLiteDF/data1.db","iris.sdf") R give this error

CentOS Errata and Bugfix Advisory 2013:1091 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-1091.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 96179f02c850f97259618f1dd3a80cc6d12b80660625dcbd6e089ccf51e50d6c sqlite-3.3.6-7.i386.rpm d78c3b102a7508754ecb5052b1da6a86de47a7b23590e3eef56164d9f3b74566

CentOS Errata and Security Advisory 2015:1635 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1635.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 172f48aba58c71b0a3c41bd8c0a459ec91a8b01f619cf118c4e64549b7e6776b lemon-3.7.17-6.el7_1.1.x86_64.rpm

CentOS Errata and Security Advisory 2020:0227 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:0227 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4e7b3e26e7960631fa1b70b58d3d363b51b0f9bee514cdd277c377750d976dd1 lemon-3.7.17-8.el7_7.1.x86_64.rpm

CentOS-5.7 SQLite-3.6.6 Ruby on Rails 3.1 Ruby-1.8.7 I have a situation wherein the version of SQLite-3 on CentOS-5 is too 'old' for the Ruby language sqlite3 DBMS adapter to successfully build against. I managed to obtain an rpm for ruby-1.8.7 but I cannot find one for sqlite-3.6.16 or later. Does anyone here have a lead on where such a beast, including the sqlite development headers,

Is there any reason (besides upstream does it) to compile php5 with --without-sqlite in CentOS5 ? Would it conflict with the sqlite that yum needs? Is there a repo (centosplus, rpmforge...) having a php5 and sqlite enabled ? I can only find older mails that seem to imply it does not harm to include sqlite (and some which seem to imply the contrary as well, but without any facts) but I can find