Skip to content

Conversation

sethdenner
Copy link

  • The way selected fields are aggregated has been refactored so that only query.select contains the selected fields and the field object is in the target attribute instead of the info attribute. I made these changes and cased it specifically for Django 1.8 leaving the legacy implementations intact.

* The way selected fields are aggregated has been refactored so that only query.select contains the selected fields and the field object is in the target attribute instead of the info attribute. I made these changes and cased it specifically for Django 1.8 leaving the legacy implementations intact.
@sethdenner
Copy link
Author

This was causing django migrations to fail. They work now in my Cassandra backend with this change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant