Re: [Django] #26730: Make AutoField consistent between postgresql and mysql

[Django]

#26730: Make AutoField consistent between postgresql and mysql
-+-
 Reporter:  hellerve |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by hellerve):

 Thanks for the heads-up. I will look into how to resolve this on my own
 then.

--
Ticket URL: 
Django 
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/066.7f576494e31383d22e81f247332a60a4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26730: Make AutoField consistent between postgresql and mysql

[Django]

#26730: Make AutoField consistent between postgresql and mysql
-+-
 Reporter:  hellerve |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MarkusH):

 FTR, I took a look at #56 during the PyCon sprints. The only sensible way
 to implement it is IMO a `PositiveAutoField`.

 The primary key column on PostgreSQL is an `integer` (-2147483648 to
 +2147483647) and the related sequence a `bigint` (-9223372036854775808 to
 +9223372036854775807) with min_value=1, max_value=9223372036854775807.
 https://www.postgresql.org/docs/9.5/static/datatype-numeric.html

 SQLite doesn't allow unsigned integers for PK columns.

 MySQL supports `integer UNSIGNED` for PK, but that's not backwards
 compatible to the existing code base.

--
Ticket URL: 
Django 
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/066.f5c816e274743859964754ef84a3eaf8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26730: Make AutoField consistent between postgresql and mysql

[Django]

#26730: Make AutoField consistent between postgresql and mysql
-+-
 Reporter:  hellerve |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => closed
 * needs_better_patch:   => 0
 * component:  Uncategorized => Database layer (models, ORM)
 * needs_tests:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * needs_docs:   => 0
 * resolution:   => duplicate


Comment:

 Duplicate of #56

--
Ticket URL: 
Django 
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/066.4f9d603e2138b6a7d4e707ff5c38d068%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26730: Make AutoField consistent between postgresql and mysql

[Django]

#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: 
Django 
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.