Add all code blocks to translation po files

1 files changed, 37 insertions, 0 deletions

diff --git a/locale/fr/LC_MESSAGES/_articles/2020-08-31-the-database-i-wish-i-had.po b/locale/fr/LC_MESSAGES/_articles/2020-08-31-the-database-i-wish-i-had.po
index 58de095..216733d 100644
--- a/locale/fr/LC_MESSAGES/_articles/2020-08-31-the-database-i-wish-i-had.po
+++ b/locale/fr/LC_MESSAGES/_articles/2020-08-31-the-database-i-wish-i-had.po
@@ -360,3 +360,40 @@ msgid ""
 "inbox/%3C010101744a592b75-1dce9281-f0b8-4226-9d50-fd2c7901fa72-000000%40us-"
 "west-2.amazonses.com%3E)."
 msgstr ""
+
+msgid ""
+"This makes me consider it as a storage backend all by itself. I\n"
+"initially considered having an SQLite storage backend as one implementation\n"
+"of the POSIX filesystem storage API that I mentioned. My goal was to rely on\n"
+"it so I could validate the correctness of the actual implementation, given\n"
+"SQLite's robustness.\n"
+"\n"
+"However it may even better to just use SQLite, and get an ACID backend\n"
+"without recreating a big part of SQLite from scratch. In fact, both Datomic\n"
+"and PouchDB didn't create an storage backend for themselves, they just\n"
+"plugged on what already existed and already worked. I'm beginning to think\n"
+"that it would be wiser to just do the same, and drop entirely the from\n"
+"scratch implementation that I mentioned.\n"
+"\n"
+"That's not to say that adding an IndexedDB compatibility layer to SQLite\n"
+"would be enough to make it fit the other requirements I mention on this\n"
+"page. SQLite still is an implementation of a update-in-place, SQL,\n"
+"table-oriented database. It is probably true that cherry-picking the\n"
+"relevant parts of SQLite (like storage access, consistency, crash recovery,\n"
+"parser generator, *etc.*) and leaving out the unwanted parts (SQL, tables,\n"
+"threading, *etc.*) would be better than including the full SQLite stack, but\n"
+"that's simply an optimization. Both could even coexist, if desired.\n"
+"\n"
+"SQLite would have to be treated similarly to how Datomic treats SQL\n"
+"databases: instead of having a table for each entities, spread attributes\n"
+"over the tables, *etc.*, it treats SQL databases as a key-value storage so it\n"
+"doesn't have to re-implement interacting with the disk that other databases\n"
+"do well.\n"
+"\n"
+"The tables would contain blocks of binary data, so there isn't a difference\n"
+"on how the SQLite storage backend behaves and how the IndexedDB storage\n"
+"backend behaves, much like how Datomic works the same regardless of the\n"
+"storage backend, same for PouchDB.\n"
+"\n"
+"I welcome corrections on what I said above, too.\n"
+msgstr ""