SQLite vs MySQL
Translations
Englishالعربية
български
català
中文
čeština
dansk
Nederlands
eesti
suomi
français
Deutsch
Ελληνικά
עברית
हिंदी
magyar
Bahasa Indonesia
italiano
日本語
한국어
latviešu
lietuvių
norsk
polski
Português
română
русский
slovenčina
slovenski
español
svenska
ไทย
Türkçe
українська
Tiếng Việt
SQLite is a single-file based database and MySQL is a normal database. That's great, but I'm not sure which is faster where or better for what...what are the pros and cons of each option?
This question and answers originated from www.stackoverflow.com
Question by Teifion (8/6/2008 4:22:32 PM)
Answer |
SQLite is great for testing and prototyping, or for embedding in applications. MySQL is worthy of (large scale) production environments.
This site has guidance on when to use SQLite
Here is my personal summary:
SQLite:
- easier to setup
- great for temporary (testing databases)
- great for rapid development
- great for embedding in an application
- not fit for production (in large scale)
- doesn't have user management
- doesn't have many performance features
- doesn't scale well.
MySQL:
- far more difficult/complex to set up
- better options for performance tuning
- fit for a production database
- can scale well if tuned properly
- can manage users, permissions, etc.
Answer by Justin Standard
Find More Answers
Related Topics mysql database sqlite comparison