Using column options internally didn't seem to really make sense for the code generation when I was looking at it. So instead we could have an alternative constructor and a way to get the members out as column options. WDYT? After looking at ColumnOptions again I am wondering if it is a good idea to "leak" them into a public api. Named arguments to def column may be a simpler alternative for user facing code.