datetime.timetuple() only includes second precision, so it was necessary to extract the microseconds separately to keep them from being lost. This fixes an issue where TimeUUID columns that were inserted with datetimes were not ordered beyond second precision.
Previously, if a validator was added to a column in a CF with a comparator_type that was not BytesType or AsciiType, the column values were not likely to be packed correctly. This affected SystemManager.create_index() and SystemManager.alter_column(). (See issue #40.)
The internal overflow count, which is negative when there are connections in the pool and overflow is enabled, can be confusing when reported in ConnectionPool.status(). Returning zero in place of a negative number helps clear this up.
These include: * get_count * multiget_count * multiget_slice
This has never been supported by Cassandra, and it was an oversight to leave this in at all.