Database Support

Ruby Apps Radiant CMS
1

Radiant’s support for different database adapters has been somewhat poor
in the past. Yes we have supported Mysql, Postgres, and Sqlite, but
migrations only ran for Mysql, and Sqlite had problems with the archive
behavior.

I just spent some time today getting Postgres up to speed again and
applied a patch that fixed the problem with the archive code for Sqlite
(in the “mental” branch).

Tests are now passing for Mysql and Postgres, but Sqlite is bombing out
on me:

Loaded suite
/Applications/Locomotive2/Bundles/standardRailsSept2006.locobundle/powerpc/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake/rake_test_loader
Started
…/Applications/Locomotive2/Bundles/standardRailsSept2006.locobundle/powerpc/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/errors.rb:94:in
`check’: SQL logic error or missing database (SQLite3::SQLException)

Which is kind of odd. Anybody have a fix for this or know what is
causing it?

Also, it looks like we will only be supporting Sqlite 3.2+. Will this be
a problem for anyone?

Anyone else have a database problem they want to report?

–
John L.
http://wiseheartdesign.com

2

On Dec 14, 2006, at 1:54 PM, John W. Long wrote:

ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/errors.rb:94:in
`check’: SQL logic error or missing database (SQLite3::SQLException)

Which is kind of odd. Anybody have a fix for this or know what is
causing it?

I get a slightly different error out of rake test:

/sw/var/lib/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/errors.rb:
94:in `check’: cannot rollback - no transaction is active
(SQLite3::SQLException)

Turning off transactional fixtures solves the error and allows most
tests to complete successfully. It does fail on one test:

test_new__post_with_parts(Admin::PageControllerTest) [./test/
functional/admin/page_controller_test.rb:123]:
<[“test-part-1”, “test-part-2”]> expected but was
<[“test-part-1”, “test-part-1”, “test-part-2”]>.

This is in mental, revision 207.

~~ Brian