Forum: Radiant CMS Any reason not to use SQLite3?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Nate T. (Guest)
on 2009-01-06 00:50
(Received via mailing list)
Since Radiant is meant for more medium scale projects, is there any real
drawback to using an SQLite3 database instead of the heavier-duty MySQL?
Sort of thinking out loud here. I have my projects now managed with git,
but
to move the database content from my local machine to the production
server
I am doing a dump then import approach. Is there a better way? Perhaps
something that can be automated into a deploy.rb file?


~Nate
Gabriel L. (Guest)
on 2009-01-06 13:51
(Received via mailing list)
Hi Nate,

As far as my experience goes, I can see no problem in using sqlite as
a production database. Indeed, my site is about 200 pages with average
of 4000 to 5000 pageviews per day and sqlite is handling it with no
problems.

The only case I wouldn't recomend sqlite is if you perform a bunch of
concurent writes to the database, then sqlite is not the tool,
otherwise if it's mainly reads sqlite will do fine.


2009/1/5 Nate T. <removed_email_address@domain.invalid>:
This topic is locked and can not be replied to.