From 75768c7479c57a401823ec1e57f1140402be8428 Mon Sep 17 00:00:00 2001 From: Adrian Sampson Date: Sun, 19 Jun 2016 13:38:15 -0700 Subject: [PATCH] Fix metadata for new post --- _config.yml | 9 +++++++++ _posts/2016-06-19-sqlite-performance.md | 4 +++- 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/_config.yml b/_config.yml index 5bc52f5e1..bab0657b1 100644 --- a/_config.yml +++ b/_config.yml @@ -6,3 +6,12 @@ highlighter: null url: http://beets.io permalink: /blog/:title.html + +defaults: + - + scope: + path: "" + type: posts + values: + layout: main + section: blog diff --git a/_posts/2016-06-19-sqlite-performance.md b/_posts/2016-06-19-sqlite-performance.md index 3eaf3aae6..09293b05e 100644 --- a/_posts/2016-06-19-sqlite-performance.md +++ b/_posts/2016-06-19-sqlite-performance.md @@ -1,4 +1,6 @@ -# we're pretty happy with SQLite & not urgently interested in a fancier DBMS +--- +title: "we're pretty happy with SQLite & not urgently interested in a fancier DBMS" +--- Every once in a while, someone suggests that beets should use a "real database." I think this means storing music metadata in [PostgreSQL][] or [MySQL][] as an alternative to our current [SQLite][] database. The idea is that a more complicated DBMS should be faster, especially for huge music libraries.