---
title: "Comment by SMTasker on \"Why Uppercasing a String Can Change Its Length\" | Hashnode"
description: "Alongside expansion, I'd test collisions in the transformed key: Python turns both 'straße' and 'strasse' into 'STRASSE'. Checking the final length helps with y"
url: "https://hashnode.com/posts/why-uppercasing-a-string-can-change-its-length/6aef68b97c81683612b4e3ca/comment/6af37b63056876d44c48f341"
---

[Discussion](https://hashnode.com/posts/why-uppercasing-a-string-can-change-its-length/6aef68b97c81683612b4e3ca)

Comment [Why Uppercasing a String Can Change Its Length](https://hashnode.com/posts/why-uppercasing-a-string-can-change-its-length/6aef68b97c81683612b4e3ca)

[SMTasker](https://hashnode.com/@smtasker)

[Nov 10](https://hashnode.com/posts/why-uppercasing-a-string-can-change-its-length/6aef68b97c81683612b4e3ca/comment/6af37b63056876d44c48f341)

Alongside expansion, I'd test collisions in the transformed key: Python turns both 'straße' and 'strasse' into 'STRASSE'. Checking the final length helps with your VARCHAR example, but it won't catch two different accepted inputs mapping to the same stored identifier. If casing is used for keys, make the uniqueness policy apply to that final representation too.
