All fields in ComposeDB models need to have strict validation, such as a max length for strings.
If you want something unrestricted, you could store the content on IPFS and store the CID of this content in a document using ComposeDB for example.
Good to know - thank you! I assume that means the columns are variable-length, so as long as the sum of all the @string is less than 256KB ascii chars I will be fine (thats plenty) and I’m not going to explode my costs (again).
Yes the columns in the underlying DB should support variable length, and indeed if the sum of all the fields being set is lower than the commit size it should be no problem.
The commits includes signatures and other metadata so you wouldn’t have the full 256KB for the content itself, better check if you get close to this limit.