Peter Ivanov

My particular use-case is that the table name is provided externally, the table itself happens to have uppercase letters in its name, so queries provided by (for example) `table.Table::Insert()` fail.

https://docs.datastax.com/en/cql-oss/3.x/cql/cql_reference/ucase-lcase_r.html Table 'What Works and What Doesn't' here describes the issue some more. If a table is created with uppercase characters, queries with lowercase name (or with uppercase name, unquoted)...

I'm not sure there isn't some subtle issues here or backwards compatibility concern that I'm not aware of, hence the issue, not a PR. Yes, I'll consider sending a PR....

We should add this feature, yes, thank you. There isn't, at the moment.

Let's. As for `Cast` itself, I believe we should split it: make a private `cast` work just as it works now, as other parts of the implementation rely on it,...

To start the discussion properly, we should examine at least a couple of real life use cases for this feature. Those could help us answer some important questions: - should...

OK, so, to make long story short, your proposal currently boils down to a public API like this: ``` func (e *Error) GetAllProperties() map[Property]interface{} { ... } ``` I'm not...

Thank you. Still, most of the argument about such API is also true for printable properties. Being 'printable' is just an optional convenience feature, a way to avoid putting the...

Thank you for the feedback. It would help if you could be a little more specific about the kind of documentation you find unsatisfactory or lacking. Would more examples help?...

Come to think of it, I agree. This is not an intended way to use the library. The issue is: this will potentially break some existing user code, which is...