Windows 10 64 bit
, can you add more details on why this is bad? Since it’s still fresh on your mind. Thank you.
I accidentally created the object because I was expecting an error to tell me which arguments I was missing when I did not give arguments.
We probably can use help here in how users would like to create a column in the context of creating a table schema. If the use case is to create the ColumnModel object, then modify it, then the creating table schema must validate the ColumnModel for ColumnType (and in some case, limit.) Otherwise, creating a ColumnModel must require sufficient information to create a valid ColumnModel. I’m more include sufficient information.
The third option is to have some default ColumnModel that user can use in creating a new ColumnModel. This maybe a nicer user interface. In any cases, the implementation should follow the use cases.