# Database Support

**URL:** <https://www.ruby-forum.com/t/database-support/102622>\
**Category:** Radiant CMS\
**Created:** [December 14, 2006, 7:58pm UTC](https://www.ruby-forum.com/t/database-support/102622 "2006-12-14T19:58:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_WSLong](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@John\_WSLong](https://www.ruby-forum.com/u/John_WSLong)\
**Post date:** [December 14, 2006, 7:58pm UTC](https://www.ruby-forum.com/t/database-support/102622/1 "2006-12-14T19:58:41Z")

</div>

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](http://wiseheartdesign.com)