22đź‘Ť
Like the others have said, this would be much easier to do on the database side than the Django side.
For Postgres, it’d be like so: ALTER SEQUENCE sequence_name RESTART WITH 12345;
Look at your own DB engine’s docs for how you’d do it there.
13đź‘Ť
For MySQL i created a signal that does this after syncdb:
from django.db.models.signals import post_syncdb
from project.app import models as app_models
def auto_increment_start(sender, **kwargs):
from django.db import connection, transaction
cursor = connection.cursor()
cursor = cursor.execute("""
ALTER table app_table AUTO_INCREMENT=2000
""")
transaction.commit_unless_managed()
post_syncdb.connect(auto_increment_start, sender=app_models)
After a syncdb the alter table statement is executed. This will exempt you from having to login into mysql and issuing it manually.
EDIT: I know this is an old thread, but I thought it might help someone.
- [Django]-How to use 'select_related' with get_object_or_404?
- [Django]-Django 1.7 migrate gets error "table already exists"
- [Django]-Laravel's dd() equivalent in django
3đź‘Ť
A quick peek at the source shows that there doesn’t seem to be any option for this, probably because it doesn’t always increment by one; it picks the next available key: “An IntegerField that automatically increments according to available IDs” — djangoproject.com
- [Django]-Django Admin – Disable the 'Add' action for a specific model
- [Django]-How to use django-debug-toolbar on AJAX calls?
- [Django]-AttributeError: 'Manager' object has no attribute 'get_by_natural_key' error in Django?
3đź‘Ť
Here is what I did..
def update_auto_increment(value=5000, app_label="xxx_data"):
"""Update our increments"""
from django.db import connection, transaction, router
models = [m for m in get_models() if m._meta.app_label == app_label]
cursor = connection.cursor()
for model in models:
_router = settings.DATABASES[router.db_for_write(model)]['NAME']
alter_str = "ALTER table {}.{} AUTO_INCREMENT={}".format(
_router, model._meta.db_table, value)
cursor.execute(alter_str)
transaction.commit_unless_managed()
- [Django]-How do I see the Django debug toolbar?
- [Django]-Custom HTTP Header in Django
- [Django]-How to simplify migrations in Django 1.7?
2đź‘Ť
I found a really easy solution to this! AutoField uses the previous value used to determine what the next value assigned will be. So I found that if I inserted a dummy value with the start AutoField value that I want, then following insertions will increment from that value.
A simple example in a few steps:
1.)
models.py
class Product(models.Model):
id = model.AutoField(primaryKey=True) # this is a dummy PK for now
productID = models.IntegerField(default=0)
productName = models.TextField()
price = models.DecimalField(max_digits=6, decimal_places=2)
- makemigrations
- migrate
Once that is done, you will need to insert the initial row where “productID” holds a value of your desired AutoField start value. You can write a method or do it from django shell.
From view the insertion could look like this:
views.py
from app.models import Product
dummy = {
'productID': 100000,
'productName': 'Item name',
'price': 5.98,
}
Products.objects.create(**product)
Once inserted you can make the following change to your model:
models.py
class Product(models.Model):
productID = models.AutoField(primary_key=True)
productName = models.TextField()
price = models.DecimalField(max_digits=6, decimal_places=2)
All following insertions will get a “productID” incrementing starting at 100000…100001…100002…
- [Django]-Django: Staff Decorator
- [Django]-What does "'tests' module incorrectly imported" mean?
- [Django]-Django templates: verbose version of a choice
1đź‘Ť
The auto fields depend, to an extent, on the database driver being used.
You’ll have to look at the objects actually created for the specific database to see what’s happening.
- [Django]-How do I package a python application to make it pip-installable?
- [Django]-Django REST Serializer Method Writable Field
- [Django]-Django 1.9 deprecation warnings app_label
1đź‘Ť
For those who are interested in a modern solution, I found out to be quite useful running the following handler in a post_migrate
signal.
Inside your apps.py
file:
import logging
from django.apps import AppConfig
from django.db import connection, transaction
from django.db.models.signals import post_migrate
logger = logging.getLogger(__name__)
def auto_increment_start(sender, **kwargs):
min_value = 10000
with connection.cursor() as cursor:
logger.info('Altering BigAutoField starting value...')
cursor.execute(f"""
SELECT setval(pg_get_serial_sequence('"apiV1_workflowtemplate"','id'), coalesce(max("id"), {min_value}), max("id") IS NOT null) FROM "apiV1_workflowtemplate";
SELECT setval(pg_get_serial_sequence('"apiV1_workflowtemplatecollection"','id'), coalesce(max("id"), {min_value}), max("id") IS NOT null) FROM "apiV1_workflowtemplatecollection";
SELECT setval(pg_get_serial_sequence('"apiV1_workflowtemplatecategory"','id'), coalesce(max("id"), {min_value}), max("id") IS NOT null) FROM "apiV1_workflowtemplatecategory";
""")
transaction.atomic()
logger.info(f'BigAutoField starting value changed successfully to {min_value}')
class Apiv1Config(AppConfig):
default_auto_field = 'django.db.models.BigAutoField'
name = 'apiV1'
def ready(self):
post_migrate.connect(auto_increment_start, sender=self)
Of course the downside of this, as some already have pointed out, is that this is DB specific.
- [Django]-How do I use Django groups and permissions?
- [Django]-How do I use the built in password reset/change views with my own templates
- [Django]-Login Page by using django forms
0đź‘Ť
I needed to do something similar. I avoided the complex stuff and simply created two fields:
id_no = models.AutoField(unique=True)
my_highvalue_id = models.IntegerField(null=True)
In views.py, I then simply added a fixed number to the id_no:
my_highvalue_id = id_no + 1200
I’m not sure if it helps resolve your issue, but I think you may find it an easy go-around.
- [Django]-Django – use reverse url mapping in settings
- [Django]-Session database table cleanup
- [Django]-Django: Multiple forms possible when using FormView?
0đź‘Ť
In the model you can add this:
def save(self, *args, **kwargs):
if not User.objects.count():
self.id = 100
else:
self.id = User.objects.last().id + 1
super(User, self).save(*args, **kwargs)
This works only if the DataBase is currently empty (no objects), so the first item will be assigned id 100 (if no previous objects exist) and next inserts will follow the last id + 1
- [Django]-Django – get user logged into test client
- [Django]-How to obtain a QuerySet of all rows, with specific fields for each one of them?
- [Django]-Django 1.8: Create initial migrations for existing schema