The string class currently consists of the following components:
- memory allocation routines (using mysys)
- binary string routines
- character set aware routines.
Storage engines (e.g. ConnectSE) often need String-alike classes, but cannot use the current String implementation because of their own memory management system. So they have to reimplement the same set of functionality, but with their own memory managers. This is bug prone and makes duplicate code.
Also, in some cases it is useful to have character-set unaware strings (just array of bytes), and static strings without allocation.
This task is to split String into logical pieces:
1. class Static_binary_string
2. class Charset
3. class Static_character_string (#1 + #2)
4. class Memory_mysys
5. template<typename MEM> class String_with_alloc
6. class String (#3 + #5)
ConnectSE will use #5 (templace class String_with_alloc), in combination with their own memory allocator.