From c9a9f7d69255d97090cd21d034cef59d4493097f Mon Sep 17 00:00:00 2001 From: Alfonso Subiotto Marques Date: Tue, 2 Sep 2025 11:05:17 +0200 Subject: [PATCH] add german strings blog post Signed-off-by: Alfonso Subiotto Marques --- content/writing/das-problem-mit-german-strings.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 content/writing/das-problem-mit-german-strings.md diff --git a/content/writing/das-problem-mit-german-strings.md b/content/writing/das-problem-mit-german-strings.md new file mode 100644 index 0000000..6e142a8 --- /dev/null +++ b/content/writing/das-problem-mit-german-strings.md @@ -0,0 +1,13 @@ +--- +title: "Das Problem mit German Strings" +date: 2025-08-26T00:00:00Z +draft: false +tags: ["databases", "performance", "storage", "optimization"] +originalPost: + site: "Polar Signals" + url: "https://www.polarsignals.com/blog/posts/2025/08/26/das-problem-mit-german-strings" +--- + +An exploration of string encoding in databases, specifically examining "German strings" and why database systems should not automatically choose encoding without considering specific use cases and workload characteristics. + +German strings are generally a great encoding choice, but not always. Context matters when it comes to selecting the optimal string encoding strategy for your database workload. \ No newline at end of file