#26730: Make AutoField consistent between postgresql and mysql
-------------------------------+--------------------
     Reporter:  hellerve       |      Owner:  nobody
         Type:  Uncategorized  |     Status:  new
    Component:  Uncategorized  |    Version:  1.9
     Severity:  Normal         |   Keywords:
 Triage Stage:  Unreviewed     |  Has patch:  0
Easy pickings:  0              |      UI/UX:  0
-------------------------------+--------------------
 '''The problem'''
 Currently, (Big)*AutoField becomes an `integer AUTO_INCREMENT` field in
 MySQL whereas it becomes a `serial` in PostgreSQL (which is a positive
 integer).

 '''The resolution?'''
 Update the MySQL version to use the `serial` datatype (which is just a
 macro for `bigint unsigned not null auto_increment unique`).

 '''Caveats'''
 The MySQL serial datatype might introduce too many unwanted restrictions.
 If the community thinks this might break too much code, I would suggest to
 at least make the MySQL version unsigned too, to increase the consistency
 between the DB adapters.

--
Ticket URL: <https://code.djangoproject.com/ticket/26730>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.4ad3f04bc34bda77e3fe0134c152b85f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to