SQLite is a powerful embedded database engine that's a core storage technology in Android and iOS applications. In this installment of the Database Clinic series—in which experts and their databases of choice are pitted against a series of the same challenges— Mark Niemann-Ross demonstrates how to leverage SQLite to solve common database problems. After providing a brief overview of the strengths and weaknesses of SQLite, Mark explains how to create a database and populate it using a public dataset. He also shows how to use a SQLite database with programming languages such as Python and R, handle subqueries and queries in SQLite, and more.
Author of "Stupid Machine" and educator at LinkedIn learningMark Niemann-Ross is a technologist with experience in hardware, software, and science fiction.
Mark has been helping developers navigate APIs for almost 30 years, and has been responsible for third-party programs at Quark and Adobe. In addition to hands-on technology, he's also been involved in technology education, starting with a degree in industrial education and most recently working as a content manager for LinkedIn Learning.
Mark's science fiction has most recently appeared in Analog Science Fiction and Fact. He's currently working on a murder mystery solved by a refrigerator.
Skills covered in this course
- [Man] SQLite does have some disadvantages. There are some SQL features omitted. For example, right join, for-each triggers, drop column, alter column, and add constraint. SQLite does not support multiple-client concurrency, users, and user permissions outside of what is provided by the operating system. SQLite does not prevent you from putting the wrong data type into a field. For example, SQLite allows you to put strings into integer fields. With these pros and cons in mind, there are times when SQLite is a good solution and other times when it isn't. Here are some rules of thumb when not to use SQLite. If you're trying to use multiple clients all accessing the same data, this may potentially cause a data crash. Frequent writes to the database are going to be slow. Concurrent writes to the database may also cause a database crash. Access over the network is not advised, it's extremely slow. And very large datasets will also cause SQLite to seize up. SQLite has a maximum of 140…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download the exercise files for this course. Get started with a free trial today.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.
Watch this course anytime, anywhere. Get started with a free trial today.