version 0.16 RC

This might not be the best way to word this. Doing Model(key=0, val=1).save() *does* work, and is useful in some narrow cases, even doing Model(key=0, val=1).update(val=2) is useful if you know what you're doing.

Maybe this would be better?

Q: Why don't updates work correctly on models instantiated as Model(field=blah, field2=blah2)? 

A: The recommended way to create new rows is with the models `.create` method. The values passed into a model's __init__ method are interpreted by the model as the values as they were read from a row. This allows the model to "know" which rows have changed since the row was read out of cassandra, and create suitable update statements. 

Thoughts?