Best way to logically partition the TransactionDB for RocksDB

[Mo0nbase]

I was recently playing around with RocksDB and I came across a particular problem that requires I use its TransactionDB. Additionally it seems to me that in RocksDB the default partitioning scheme is handled by this thing they call column families which is a very convenient and relatively safe way to partition the database in lieu of running separate databases. Now I was wondering how to effectively use column families within TransactionDB because although I think TransactionDB is inherited from RocksDB's normal K,V database i'm not sure if it includes support for this feature. Now I could partition the TransactionDB by using key spaces based on prefixing to define my different sections, or I could run multiple databases but these solutions are quite inconvenient and aren't nearly as safe. In this case I would be responsible for handling all the checks to make sure my transactions don't overflow in to other key spaces or in the case of using multiple databases I would have to make sure they were all kept in the correct synced state and that there were no extra losses to failed rw operations. Anyway I was simply wondering what the correct way to go about this is? Does TransactionDB already support column families? or am i expected to do one of these two things? or something else?