Plays via YouTube's privacy-enhanced embed

An Introduction to SQLite

Name: An Introduction to SQLite
Description: A 2006 Google TechTalk in which SQLite's author Richard Hipp introduces the embeddable, zero-configuration C database library. He covers its history, strengths and weaknesses, and where it beats client/server databases.

Google TechTalks

56 videos recommended on HN

YouTube

1 HN user recommended this talk1 month2011–2018 score 1

Years with an HN recommendation, 2007–2026

Recommended as a first-hand intro from SQLite's creator that also teaches how a database engine is built.

A 2006 Google TechTalk in which SQLite's author Richard Hipp introduces the embeddable, zero-configuration C database library. He covers its history, strengths and weaknesses, and where it beats client/server databases.

“is actually a pretty good intro on to how to build your own DB engine.” (HN, 2016)

1 recommendations · 2 citations · Talks · intro · partly dated

Databases & storage Talks Systems, Networks & Security

3 Hacker News comments

From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.

@simscitizen Oct 2016 Recommends

on HN thread Ask HN: What's your favorite tech talk?

"An Introduction to SQLite" by Richard Hipp (who wrote the library) is actually a pretty good intro on to how to build your own DB engine. [this video]

Intro by SQLite's author that doubles as a guide to building a DB engine.

View on Hacker News

Citations, criticism and jokes

@hendler Apr 2011 Cites it

on HN thread IndexedDB has much to learn from SQLite

I've also worked with SQLite, and one project was the using the C API. It's also why I really liked Google Gears. Here's the Google Tech Talk on SQLite from 2006 [this video]

Google Tech Talk introducing SQLite from 2006.

View on Hacker News

@dahart Aug 2018 Cites it

on HN thread Ask HN: Codebase at my work is a complete mess, what should I do?

First start writing automated tests, for example Selenium & unit tests. You'll learn what all the code does, you'll learn a new skill, you'll have a safety net of regression tests for rewriting the code, and you'll be adding value to the company. If you have good test coverage, you'll be able to rewrite the code very quickly. There are a ton of resources for how and why to do testing. One that stands out in my mind is SQLite. They've talked about being able to refactor the core of their engine in a weekend, only because they had the test coverage to know they did it right. [link] [link] [this video]

SQLite cited as example of test coverage enabling big refactors.

View on Hacker News