make the keyspace threadsafe and use a connection pool to make it work with sidekiq
smaller connection pools
fix specs
bump version
allow erb yml files
support initial creation of cassandra keyspace
fix thread safety for scopes
Take debugger out
Load multiple dictionary rows in one query
Counter column support for data sets
Merge branch 'master' of github.com:brewster/cequel

* 'master' of github.com:brewster/cequel:
  fix thread safety for scopes
  bump version
  fix specs
  smaller connection pools
  make the keyspace threadsafe and use a connection pool to make it work with sidekiq

Conflicts:
	Gemfile.lock
Cequel::Model::Counter model class
Merge pull request #2 from ping4/erb_yml_files

allow erb yml files
Merge pull request #3 from ping4/inital_keyspace

support initial creation of cassandra keyspace
Merge branch 'master' of github.com:brewster/cequel

* 'master' of github.com:brewster/cequel:
  support initial creation of cassandra keyspace
  allow erb yml files
Credit where credit is due
Update README for counter support
Revert back to instance-level use of Keyspace

Keyspace isn't meant to be globally configured; each Keyspace instance
can have a connection pool, which is lazily created if the configuration
specifies a pool size. Otherwise, it just lazy-initializes a single
instance variable, leaving it up to the user to make sure keyspaces are
being used in a thread-safe way.
Remove #create and #drop methods

These don't work with the restored keyspace-instance-variable setup, and
I'd like to think more about the most logical way to implement them.
Also want to support strategy options.
Bump version