Fix MutableByteArrayHandler placement and update readme info

Relocated MutableByteArrayHandler implementation to correct position in ByteArrayHandler file for better organization. Updated readme to clarify behavior when updating variable-length types like strings for improved compression efficiency.
This commit is contained in:
2024-12-13 22:00:00 +01:00
parent c64df75cd5
commit 69fa23a7a9
2 changed files with 47 additions and 46 deletions

View File

@@ -42,7 +42,7 @@ class Person : TypedByteArray(
```
The different between STRING and CLOB is the maximum size (32kb vs 2gb). For any type where the length isn't fixed we need to provide max size.
When for example a string is updated with a shorter string the remaining bytes are zeroed to make compression as efficient as possible.
When such a type is updated, for example we update a string with a shorter string the remaining bytes are zeroed to make compression as efficient as possible.
Strings are stored as UTF-8 bytes, there is also a CachedStringProperty which will keep a copy of the string so it isn't converted to a
native string every time it's accessed.