Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bigint AutoField (fixes #56, #13774) #62

Closed
wants to merge 1 commit into from

Conversation

Projects
None yet
2 participants
@pzinovkin
Copy link

commented May 13, 2012

Alternative approach to fix ticket 56.
Based on discussion #49
This approach doesn't change AutoField behavior. Only those who need extended int range may use it.
It keeps values ranges consistent between databases. Also it works nice with related fields.

@akaariai

This comment has been minimized.

Copy link
Member

commented Jul 16, 2012

To me it seems this needs some tests, mainly one for checking that the foreign key to a bigautofield is created properly as bigint. As per the policy of "commit or close when reviewing" I am closing this pull request.

@akaariai akaariai closed this Jul 16, 2012

sztrovacsek pushed a commit to sztrovacsek/django that referenced this pull request Mar 7, 2015

jomuda pushed a commit to jomuda/django that referenced this pull request Apr 6, 2019

Merge pull request django#62 from scummboy/develop
Update !gifr to use Giphy's random API call
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.