use an actual schema for storing tag data

3 files changed, 16 insertions, 2 deletions

diff --git a/example/internal_tables.md b/example/internal_tables.md
new file mode 100644
index 0000000..a43b806
--- /dev/null
+++ b/example/internal_tables.md
@@ -0,0 +1,14 @@
+Underwriter uses SQLite to store tag information. The database structure
+is based off of the ["Toxi"][1] schema.
+
+[1]: http://howto.philippkeller.com/2005/04/24/Tags-Database-schemas/
+
+The three tables used are
+
+* `cards`, containing the name and creation date
+* `tags`, containing an ID of the tag and the name
+* `tagmap`, where each row matches a card with a tag
+
+The `tagmap` is many-to-many. For instance, if `X` is a member of
+`cards`, and `Y`, `Z` are members of tags, then `(X,Y)` and
+`(X,Z)` can be members of `tagmap`.
diff --git a/example/tag_idempotent.md b/example/tag_idempotent.md
index 07c695c..f8fa64f 100644
--- a/example/tag_idempotent.md
+++ b/example/tag_idempotent.md
@@ -1,5 +1,5 @@
 It is fine to add the same tag multiple times to a card: `underwriter`
 will merge multiple tag mentions.
 
-    underwriter tag tag_idempotent.md usage example command command
-    underwriter tag tag_idempotent.md usage usage example example
+    underwriter tag tag_idempotent.md usage example example
+    underwriter tag tag_idempotent.md usage feature
diff --git a/example/underwriter.db b/example/underwriter.db
index f04ccb7..5d1c961 100644
--- a/example/underwriter.db
+++ b/example/underwriter.db