It's up to you, really. The serialized selection is made up of some fixed length stuff (checksum, separator character) plus two serialized selection boundaries, which could be any length but take the form a/b/c/..... where each of a, b, c etc. is a child node index allowing the deserializer to drill down through the DOM from the document at the top to get to the node containing the selection boundary. In practice, unless you have a really deeply nested DOM, you could probably get away with a generous character limit (100 would be plenty, I'd imagine) on the database field.
Tim