Using SQLite vs. MySQL with Ruby?

Question

I am new to Ruby and wondering if most people are using the SQLLite db that seems to be the most natural and recommended db to use with Ruby? Or are people using the traditional MySQL db?

What are the benefits/drawbacks of each with Ruby?

Thanks, Alex

Robert Harvey · Accepted Answer · 2011-04-25 18:26:57Z

13

SQLite is used primarily for development purposes only because it is quite simple to setup a database without much frustration, however it is certainly less efficient in terms of concurrency (which is highly likely for web applications) than something like MySQL. So regardless if you use SQLLite in development or not, it is highly advisable to use MySQL (or something equivalent) in production.

For completeness sake, SQLite is also used in "all in one package" software (such as mobile development), in which you can easily bundle a SQLite file with your application.

As stated on SQLite Website:

SQLite is not intended to be an enterprise database engine. It is not designed to compete with Oracle or PostgreSQL.

and

Another way to look at SQLite is this: SQLite is not designed to replace Oracle. It is designed to replace fopen().

In terms of the benefits with Ruby, there really isn't much benefit as libraries/ORMs (i.e. Active Record) really abstract the differences between the two systems to make a consistent access layer in a single wrapper.

edited Apr 25, 2011 at 18:26

Robert Harvey

182k48 gold badges349 silver badges516 bronze badges

answered Apr 25, 2011 at 18:10

Mike Lewis

64.3k20 gold badges144 silver badges111 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

user142019 Over a year ago

Isn't SQLite much, much faster than MySQL?

Mike Lewis Over a year ago

In MySQL you can do tons of performance tunings, stored procedures, access control(with users and permissions) etc.

Wiseguy Over a year ago

SQLite is exceptionally portable, and although it's not as powerful as MySQL in several ways, it's more than sufficient for the majority of sites. Pros and cons will vary per individual needs.

Wiseguy Over a year ago

+1 Complete and well said. Useful and acceptable for simple stuff, but better to use a full RDBMS if that's what you need.

mu is too short Over a year ago

I'd say it is highly advisable to use exactly the same database for development and production. Always. No ORM can protect you against database differences (hence all the "it broke when I put it on Heroku" questions).

Community · Accepted Answer · 2017-05-23 12:01:40Z

4

SQLITE is cool for desktop applications, mobile applications, and for development :) because it is easy to install and to manage, also it stores all data in one file, which is easy to copy.

But it is a bad choice for production. It doesn't support parallel acces for writing. As bigger file, as slower queries. Problems with scaling. And a number of other problems.

See this topic for more information

https://stackoverflow.com/questions/3630/sqlite-vs-mysql

edited May 23, 2017 at 12:01

CommunityBot

11 silver badge

answered Apr 25, 2011 at 18:15

fl00r

83.7k33 gold badges222 silver badges239 bronze badges

Comments

retro · Accepted Answer · 2011-04-25 18:11:25Z

1

In rails, you are using ActiveRecord ORM. Many developers are using sqlite adapter for development with ActiveRecord, because it is very easy to setup it.

answered Apr 25, 2011 at 18:11

retro

3,8132 gold badges22 silver badges37 bronze badges

Collectives™ on Stack Overflow

Using SQLite vs. MySQL with Ruby?

3 Answers 3

5 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

5 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related