Skip to content

Commit f21aca6

Browse files
authored
Fix slightly snide comment about SQLite
The original language implies that SQLite is not an "actual" database engine, which is of course not the case! SQLite is a very capable and ubiquitous database engine. It's not appropriate for many applications, though, so perhaps the document here can simply read "different" rather than "actual". I recognize this is a bit particular, but hey-- that's how I perceived the language on my first read, and I don't even particularly like (or use) SQLite anyways! I do respect the technology, though, and thought it'd be kind to change the language so as to remove all possibility of misinterpretation.
1 parent 823b0d4 commit f21aca6

File tree

1 file changed

+1
-1
lines changed
  • docs/tutorial/persisting-our-data

1 file changed

+1
-1
lines changed

docs/tutorial/persisting-our-data/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ There are two main types of volumes. We will eventually use both, but we will st
7474
By default, the todo app stores its data in a [SQLite Database](https://www.sqlite.org/index.html) at
7575
`/etc/todos/todo.db`. If you're not familiar with SQLite, no worries! It's simply a relational database in
7676
which all of the data is stored in a single file. While this isn't the best for large-scale applications,
77-
it works for small demos. We'll talk about switching this to an actual database engine later.
77+
it works for small demos. We'll talk about switching this to a different database engine later.
7878

7979
With the database being a single file, if we can persist that file on the host and make it available to the
8080
next container, it should be able to pick up where the last one left off. By creating a volume and attaching

0 commit comments

Comments
 (0)