Function: User Data
This doesn't actually need any specialized tables; it just makes use of TextFerret.
- "User data" is really just key-value pairs that are also tagged for a specific user.
- As such, they could just be tf_nodes with a key-leaf (text), a value-leaf (arbitrary but usually text), and a user-leaf (int for user ID), all handled by a particular code class (as intended).
- If you want to store a bunch of data for a particular user all together instead of as individual nodes, it could be serialized -- but only do this if there will rarely be any need to access just a few of the components individually, since the entire serialized dataset will need to be accessed each time.