Wrote tests to exercise Django ForeignKey creation and queries.
Refactored AutoFieldUUID auto value creation into a method on the field class called "get_auto_value"
In the case that the default Django AutoField is being used the database backend now counts the current rows in the column family and then sets the new insert. Auto-incrementing integer fields really only work on single node Cassandra clusters or clusters that replecate data across all nodes before responding not to mention counting the rows is expensive and not scalable. I pretty much just added this for compatibility, there could be a more efficient way to implement this.
In all other cases the database backend looks for the "get_auto_value" method to be defined on the custom auto field.
Updated "Usage" documentation.
Fixed a bug where the backend couldn't properly determine that an order_by statement is efficent due to it not checking if the partition key has been filtered or not yet correctly.