NoSQL

Issue Creation Checklist

• I have read the contribution guidelines

Feature Description

When SQL errors occur, make the 'mes

The observable class keeps the list of std::function<void(Args...)> subscribers onboard. When set (called) the value notifies all observers about the change. Being void the callback that needs to start an asynchronous operation can do nothing but send it into the background by ignoring the top-most future. It would be nice if observable::operator() returned back a future. This would requir

I'm not sure how feasible this may be, but the old logparser program from Microsoft supported queries like

Select * from test.csv

And it would read from test.csv, without needing any config files.

Hey Crew,

Nice job on gocql, I'm a fan...

For my production services, I could use notification events (via callback or channel) when the gocql client disconnects and reconnects to/from Cassandra. This is useful for higher-level application logic (ie: invoke alarms, stop reading from a durable message queue, etc).

After looking through the code, it looks like the connection information is not p